safe-chain
1.5.15 open-sourceThe section your link pointed to isn't on safe-chain's page any more, so we've brought you to the top.
Aikido Safe Chain blocks malware in npm and PyPI packages on developer laptops and CI/CD by intercepting downloads through a local proxy.
safe-chain install -is-mdm npx safe-chain rush safe-chain --install-dir /custom/path/to/install safe-chain scan --npm-min-age=7d safe-chain scan --pypi-min-age=7d export CI_PROVIDER=circleci safe-chain scan pipx install safe-chain export NPM_CONFIG_REGISTRY=https://private-registry.example.com/ safe-chain scan --source ./my-node-app safe-chain python --minimum-package-age 0 . ./scripts/uninstall.sh safe-chain setup --include-python pip install <package-name> --safe-chain-skip-minimum-package-age safe-chain --silent scan --target ./my-app safe-chain --version safe-chain install --safe-chain-malware-action=prompt
Summary
safe-chain is an open-source command-line tool that intercepts npm and PyPI package installs to block malware before it lands on a developer's machine, and it costs nothing to run. It wraps common package manager commands (npm, yarn, pnpm, bun, pip, poetry, uv, and others) and blocks known-malicious packages and anything published in the last 48 hours, without a token or shared build data. It's aimed at application developers and the teams securing CI/CD pipelines against supply-chain attacks, rather than at security analysts reviewing findings after the fact. For organisations wanting centralized policy and coverage beyond npm and PyPI, the same vendor offers a separate device-protection product built on top of it. First committed in 2025, safe-chain has seen over a thousand commits and 17 releases in the past year, with the last one 38 days ago.
Aikido Safe Chain blocks malware in npm and PyPI packages on developer laptops and CI/CD by intercepting downloads through a local proxy.
How safe-chain helps
Is the package I'm about to add safe to install, or does it need a closer look first?
checks the package name and version against the malicious-package feed and blocks the install before it reaches disk if it matches
Could this install slip a newly-published malicious package past me before anyone's had a chance to flag it?
blocks anything published in the last 48 hours regardless of whether it has been reported yet, so brand-new packages can't land during that window
Is my CI/CD pipeline exposed to the same supply-chain risk as a developer's laptop?
wraps the same package manager commands in both places, so installs are checked the same way in a pipeline as on a workstation without needing a token or shared account
Which package managers in my stack are actually covered by this protection?
intercepts npm, yarn, pnpm, bun, and their runners, plus pip, poetry, uv, pipx and pdm, so mixed-toolchain projects get the same check regardless of which command a developer or script reaches for
Do I need to share build data or credentials for installs to get checked?
runs the check locally against the malicious-package feed without a token or any build data leaving the machine
Do I need a separate product to get this protection outside of npm and PyPI?
on its own it only covers npm and PyPI; broader ecosystem and centralized policy across a fleet comes from a separate product built on top of it
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for safe-chain, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail safe-chain puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Commercials
pricing & packaging history · Aikido Security vendor page30 readings of Aikido Security's pricing page since Mar 2023, with 13 relaunches of its plan lineup and 15 changes to what its plans include — each one dated, compared with the reading before it, and explained for someone buying the tool.
Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.
See plans → Already subscribed? Sign in →Plans by offering
Each offering on the pricing page links to its own page of plans, read at its latest capture.
Plan relaunches
Plans, prices and descriptions are quoted from the vendor's own pricing page as we read it on each date. A plan missing from a later reading is shown as no longer listed on the page — a statement about the page, not the product. Readings that failed to show any plans are left out rather than read as a change.
Website history
aikido.dev, every changeAikido Security's home, pricing and product pages and 40 more pages as they looked each month from December 2022 to October 2026: 122 renders, 19 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
18 entries
No entries match these filters.
- August 20261
- June 20262
- May 20261
- April 20261
- March 20261
- February 20261
- January 20262
- December 20253
- November 20251
- October 20253
- September 20252
Project health
Issue, contributor and maintainer activity in AikidoSec/safe-chain, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 26 +22 vs prior 12 months
- Maintainers 3 +2 joined · −0 left, last 12 months
- Bus factor 2 committers behind half the commits
- Community-filed 88% of issues opened, last 12 months
- Median time to close 7.8 days first maintainer reply 24 hours
- Open backlog 79 of 198 issues ever filed
- Issues opened / month 1 · 0 communitymaintainers
- Open backlog 79
- Contributors / month 5
- Commits / month 33
- Stars 1,762
- bugs 45%
- features 5%
- other 50%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.