@devicefarmer/stf-device-dbnpm
- latest 2.0.0
- last known licence (CC-BY-SA-4.0 AND Apache-2.0)
- stars 3
- assessment attempted 7 days ago
- GitHub evidence observed 7 days ago
- registry checked 7 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 3 years without a release, @devicefarmer/stf-device-db published 2.0.0 on 2026-10-26.
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, 2.0.0, carries a signed provenance attestation. Source: the registry.
- Supported runtime — node >= 22.12. Source: the registry.
- Publishers on the registry — 2. Source: the registry.
Third-party facts checked 20 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-29 | first verdict: finished |
Licence history 1
| When | Change | Severity |
|---|---|---|
| 2026-10-29 | CC-BY-SA-4.0 → CC-BY-SA-4.0 AND Apache-2.0 (2.0.0) | warning |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@devicefarmer/stf-device-db)Watch it
Get told when @devicefarmer/stf-device-db 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.