Retire.js
6.1.0 open-sourceThe section your link pointed to isn't on Retire.js's page any more, so we've brought you to the top.
Retire.js scans JavaScript libraries and Node.js modules to identify versions with known security vulnerabilities.
retire --outputformat cyclonedxJSON1_7 retire --outputformat cyclonedxJSON1_7_VEX --exitwith 0
Summary
Retire.js is an open-source dependency-scanning tool that checks JavaScript libraries and Node.js modules for known vulnerabilities, addressing the OWASPOWASPA nonprofit foundation that publishes open standards, guides, and ranked vulnerability lists—most famously the OWASP Top 10—giving cyber tools a vendor-neutral benchmark to test or report against. Top 10 risk of using components with known flaws. It runs primarily as a command-line scanner installed via npm, with a scan producing either console output or a CycloneDXCycloneDXAn open standard for describing software components and their dependencies, vulnerabilities and other supply-chain information. Tools use it to exchange bills of materials and related evidence. SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue., though the project also ships (with varying degrees of maintenance) as a Chrome extension, a Burp/ZAP add-on, and a formerly-supported Firefox extension. It is aimed at application developers and appsec teams who need to catch vulnerable frontend and Node dependencies that package manifests miss, particularly libraries just dropped into source control. First committed in 2013, it remains active, with 118 contributors and 174 commits in the past year across 11 releases.
Retire.js scans JavaScript libraries and Node.js modules to identify versions with known security vulnerabilities.
How Retire.js helps
Which of my JavaScript files came from a vulnerable library that never showed up in a manifest?
walks the source tree checking file contents and hashes against a vulnerability database, catching libraries that were copied in directly rather than installed through a package manager
Do any of my Node modules have known vulnerabilities?
matches installed module versions against the same vulnerability repository and lists each one with its severity, so nothing is missed just because it is a backend rather than a frontend dependency
Should this build fail because of what got flagged?
lets the severity threshold decide what counts as a failure and exits with a distinct code when anything at or above it is found, so a pipeline can gate on it directly
Can I hand this list of dependencies to another security tool or team?
produces a CycloneDX-format bill of materials with each detected component, the technique and confidence used to identify its version, and which repository the vulnerability data came from
Is a visitor's browser loading an insecure library on a site I didn't build myself?
the browser extension inspects the libraries a page actually loads at visit time and flags known-insecure ones in the developer console and address bar icon
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
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for Retire.js, 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 Retire.js 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…
Releases
6 entries
No entries match these filters.
- October 20261
- August 20263
- May 20231
- April 20151
Project health
Issue, contributor and maintainer activity in RetireJS/retire.js, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 5 −1 vs prior 12 months
- Maintainers 1 +0 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close < 1 day first maintainer reply 19 hours
- Open backlog 2 of 280 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 2
- Contributors / month 2
- Commits / month 5
- Stars 4,173
- bugs 17%
- features 17%
- other 66%
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
Articles
1 article · updated Nov 4, 2026Where Retire.js turns up in what others publish: how-tos, attack reports that name it, and incident write-ups. A row says why it is here and quotes where the article names it; the link goes to the publisher.
Tutorials & guides 1
-
Burp Suite for Pentester: Software Vulnerability Scanner & Retire.js
Retire.js Dynamic web applications typically include a variety of libraries, whether they use React , Angular , or jQuery .
2 more quotes
For the analysis part, we have another powerful Burp Suite plugin called Retire.js .
As the name suggests, Retire.js is designed to identify retired or outdated (and potentially vulnerable) versions of JavaScript libraries used by the application.
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.