@celo/odis-identifiersnpm
- latest 1.0.1
- last known licence Apache-2.0
- stars 12
- assessment attempted 15 days ago
- GitHub evidence observed 15 days ago
- 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 →Came back
After 2 years without a release, @celo/odis-identifiers published 1.0.1 on 2026-10-07.
Usually this is a maintainer returning. It is also what a hijacked package looks like, so it is worth a glance at what changed before you upgrade.
Maintenance trends
Loading historical repository activity…
Signals · last 2 checks
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Publishers on the registry — 4. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — 3 - Celo MVP Testnet; 5 - Celo MVP Mainnet 5/5 done; 6 - Post MVP Mainnet 3/3 done; 4 - Celo Alfajores migration 7/7 done; Celo Sepolia (due 2025-09-30) 1/1 done. Source: the repository's milestones.
Third-party facts checked 15 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-23 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@celo/odis-identifiers)Watch it
Get told when @celo/odis-identifiers 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.