@hasura/metadata-apinpm
- latest 0.1.0-prerelease.2
- last known licence Apache-2.0
- stars 32,125
- assessment attempted yesterday
- GitHub evidence observed yesterday
- 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 11 checks
Commits 90d
100
Open issues
2212
Unanswered
773
Contributors
8
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Publishers on the registry — 1. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — Next 0/3 done; Now (in progress) 17/26 done; Later 0/14 done. Source: the repository's milestones.
- OpenSSF Scorecard — 5.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 9 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-08 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@hasura/metadata-api)Watch it
Get told when @hasura/metadata-api 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.