@frankfmy/db-utilsnpm
- latest 2.0.0
- last known licence Apache-2.0
- stars 1
- assessment attempted 2 days ago
- GitHub evidence observed 2 days ago
- registry checked 2 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 1 check
The first observation is recorded. Trend lines appear once at least two checks have data for the same signal.
Commits 90d
6
Open issues
0
Unanswered
0
Contributors
1
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.
Third-party facts checked 2 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-06 | first verdict: active |
Licence history 1
| When | Change | Severity |
|---|---|---|
| 2026-11-06 | PolyForm-Shield-1.0.0 → Apache-2.0 (2.0.0) | info |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@frankfmy/db-utils)Watch it
Get told when @frankfmy/db-utils 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.