Is cors healthy, maintained, and safe?
Mostly yes — cors is maintained, with a couple of watch-items rather than red flags.
The verdict
On the OSPulse health scale, cors lands at 70/100 — low risk, computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Mostly yes — cors is maintained, with a couple of watch-items rather than red flags.
The newest release dates to 22 January 2026, 186 days back — a gap long enough to suggest the pace is slowing. Historically it released far more frequently, so the current silence reads as a genuine collapse in velocity rather than a natural gap. 3 maintainers are listed on npm, so the project isn't hostage to any single contributor.
Security-wise, cors currently has a clean OSV record — no published advisories. Keep in mind that reflects what's been disclosed, not a guarantee of safety.
A couple of watch-items aside, cors is a reasonable dependency to rely on; keep an eye on the flagged signals. 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
- v2.8.6
- Last release
- 22 January 2026 (186 days ago)
- Total releases
- 35
- First release
- 31 January 2013
- Package age
- 13.5 years
- Maintainers
- 3
- Known advisories
- 0
- Confidence
- High
Frequently asked
Is cors still maintained?
Partly — the most recent release was 22 January 2026 (186 days ago), so maintenance has slowed but not fully stopped.
Does cors have known security vulnerabilities?
No advisories are currently recorded for cors in the OSV database. That means none have been publicly disclosed and indexed — it is not a guarantee of safety.
Is cors safe to use?
Mostly yes — cors is maintained, with a couple of watch-items rather than red flags. OSPulse rates it 70/100 (low risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
cors 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.