@rio-cloud/biome-config-claidnpm
- latest 1.0.1
- last known licence Apache-2.0
- assessment attempted 25 days ago
- registry checked 25 days ago
- registry ↗
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 15 months without a release, @rio-cloud/biome-config-claid published 1.0.0 on 2026-09-30.
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 3 checks
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node >=24. Source: the registry.
- Publishers on the registry — 5. Source: the registry.
Third-party facts checked 29 days ago; registry facts on every crawl.
State history 2
| When | Change |
|---|---|
| 2026-10-18 | unknown → active |
| 2026-09-13 | first verdict: unknown |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@rio-cloud/biome-config-claid)Watch it
Get told when @rio-cloud/biome-config-claid 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.