Is browserify healthy, maintained, and safe?
Maintained, but watch it — browserify has real signals (drift, thin maintenance, or advisories) worth tracking.
The verdict
OSPulse scores browserify at 55/100 (medium risk), computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Maintained, but watch it — browserify has real signals (drift, thin maintenance, or advisories) worth tracking.
Nothing has shipped since 3 October 2024 — over a year ago (661 days) — which points to a dormant project. Historically it released far more frequently, so the current silence reads as a genuine collapse in velocity rather than a natural gap. 40 maintainers are listed on npm, so the project isn't hostage to any single contributor.
On the security side, OSV has no advisories on record for browserify today. That's reassuring, but "no known advisory" is not the same as "no vulnerability" — it only means nothing has been disclosed and indexed yet.
browserify is usable but carries real signals — pin versions, watch for new advisories, and keep a fallback in mind. This is a one-time snapshot of a single package — real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own package.json through the free health check, or have OSPulse monitor your whole dependency tree continuously.
Evidence trail — deterministic, auditable
Key facts
- Latest version
- v17.0.1
- Last release
- 3 October 2024 (661 days ago)
- Total releases
- 485
- First release
- 3 February 2011
- Package age
- 15.5 years
- Maintainers
- 40
- Known advisories
- 0
- Confidence
- High
Frequently asked
Is browserify still maintained?
Partly — the most recent release was 3 October 2024 (661 days ago), so maintenance has slowed but not fully stopped.
Does browserify have known security vulnerabilities?
No advisories are currently recorded for browserify in the OSV database. That means none have been publicly disclosed and indexed — it is not a guarantee of safety.
Is browserify safe to use?
Maintained, but watch it — browserify has real signals (drift, thin maintenance, or advisories) worth tracking. OSPulse rates it 55/100 (medium risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Alternatives to browserify
Other npm packages we've checked
browserify is one package. What about the other hundreds in your tree?
Paste your own package.json into the free health check for an instant snapshot — or let OSPulse monitor your whole dependency tree continuously, before your CVE scanner wakes up.
Data from the npm registry & OSV.dev · snapshot generated 2026-07-27 · scores are deterministic and recomputed on each refresh.