Is passport healthy, maintained, and safe?
No — passport looks abandoned and still has open security advisories.
The verdict
On the OSPulse health scale, passport lands at 17/100 — critical risk, computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. No — passport looks abandoned and still has open security advisories.
The last sign of life was 27 November 2023, more than 2 years ago (1014 days); by any practical measure the package looks abandoned. Historically it released far more frequently, so the current silence reads as a genuine collapse in velocity rather than a natural gap. Ownership rests on a single maintainer — a bus-factor of one, meaning one person's availability is a single point of failure for everyone downstream.
OSV lists 1 known advisory for passport, of assorted severity. Review whether your version is in the affected range and whether a fixed release is available before depending on it. Each advisory is listed with its OSV/GHSA identifier below.
The safest reading is to replace, fork, or tightly pin passport and stop taking on new exposure to it. 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
Known vulnerabilities (1)
Passport vulnerable to session regeneration when a users logs in or out
Key facts
- Latest version
- v0.7.0
- Last release
- 27 November 2023 (1014 days ago)
- Total releases
- 33
- First release
- 8 October 2011
- Package age
- 14.9 years
- Maintainers
- 1
- Known advisories
- 1
- Confidence
- High
Frequently asked
Is passport still maintained?
It doesn't appear to be — the last release was 27 November 2023, over two years ago, which usually indicates an abandoned package.
Does passport have known security vulnerabilities?
Yes — OSV lists 1 advisory for passport. See the advisory list on this page for the OSV/GHSA identifiers.
Is passport safe to use?
No — passport looks abandoned and still has open security advisories. OSPulse rates it 17/100 (critical risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Alternatives to passport
Other npm packages we've checked
passport 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-09-07 · scores are deterministic and recomputed on each refresh.