@datanimbus/mongoosenpm
- latest 6.13.10
- last known licence MIT
- stars 27,450
- assessment attempted yesterday
- GitHub evidence observed yesterday
- registry checked 18 days ago
- registry ↗
- repository ↗
Vulnerabilities, end of life and next steps
Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.
Review remediation options →Maintenance trends
Loading historical repository activity…
Signals · last 10 checks
Commits 90d
100
Open issues
170
Unanswered
28
Contributors
10
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=12.0.0. Source: the registry.
- Publishers on the registry — 4. Source: the registry.
- Funding — opencollective.com/mongoose. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — Parking Lot 3/33 done; 8.x Unprioritized 6/88 done; TypeScript backlog 0/2 done; 10.0 18/26 done; 9.12 3/5 done. Source: the repository's milestones.
- OpenSSF Scorecard — 6.6 / 10 on 2026-08-24. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.
Third-party facts checked 7 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-07 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@datanimbus/mongoose)Watch it
Get told when @datanimbus/mongoose changes state, changes licence, or is deprecated — instead of finding out during an incident.
Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.