@provisioner/docker-registrynpm
- latest 0.0.31
- last known licence Apache-2.0
- stars 4
- assessment attempted 5 days ago
- GitHub evidence observed 5 days ago
- registry checked 12 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 2 checks
Commits 90d
0
Open issues
33
Unanswered
31
Contributors
0
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.
- Open milestones — Custom Provisioners Public Preview; AppEngine Public Preview (due 2021-02-17) 12/12 done; AppEngine vNext (due 2021-03-03) 1/11 done. Source: the repository's milestones.
- OpenSSF Scorecard — 2.9 / 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 5 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-01 | first verdict: abandoned |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@provisioner/docker-registry)Watch it
Get told when @provisioner/docker-registry 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.