@helveg/typeormnpm
- latest 0.3.21
- last known licence MIT
- stars 36,672
- assessment attempted today
- GitHub evidence observed today
- registry checked 14 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 20 checks
Commits 90d
41
Open issues
479
Unanswered
126
Contributors
32
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=16.13.0. Source: the registry.
- Publishers on the registry — 1. Source: the registry.
- Funding — opencollective.com/typeorm. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — Future 3/13 done; Community 10/14 done; Next 1/1 done; 2.0.next 46/46 done. Source: the repository's milestones.
- OpenSSF Scorecard — 7.2 / 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 14 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-09 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@helveg/typeorm)Watch it
Get told when @helveg/typeorm 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.