Is cross-env healthy, maintained, and safe?
Maintained, but watch it — cross-env has real signals (drift, thin maintenance, or advisories) worth tracking.
The verdict
OSPulse scores cross-env at 55/100 (medium risk), computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Maintained, but watch it — cross-env has real signals (drift, thin maintenance, or advisories) worth tracking.
The newest release dates to 29 September 2025, 302 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. 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.
On the security side, OSV has no advisories on record for cross-env 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.
cross-env 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
- v10.1.0
- Last release
- 29 September 2025 (302 days ago)
- Total releases
- 50
- First release
- 1 October 2015
- Package age
- 10.8 years
- Maintainers
- 1
- Known advisories
- 0
- Confidence
- High
Frequently asked
Is cross-env still maintained?
Partly — the most recent release was 29 September 2025 (302 days ago), so maintenance has slowed but not fully stopped.
Does cross-env have known security vulnerabilities?
No advisories are currently recorded for cross-env in the OSV database. That means none have been publicly disclosed and indexed — it is not a guarantee of safety.
Is cross-env safe to use?
Maintained, but watch it — cross-env 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.
Other npm packages we've checked
cross-env 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-28 · scores are deterministic and recomputed on each refresh.