@cap-js/db-servicenpm
This package has dated incident reports relevant to its trust history. Check the affected releases and the response before drawing conclusions about its current version.
Read the incident coverage →- latest 3.1.2
- last known licence Apache-2.0
- stars 53
- assessment attempted 26 days ago
- registry checked 21 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 10 checks
What the project says about itself
- Build provenance — the latest release, 3.1.2, carries a signed provenance attestation. Source: the registry.
- Publishers on the registry — 3. Source: the registry.
- Security policy — published. Source: the repository.
Third-party facts checked 26 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-12 | first verdict: active |
Supply-chain history 1
-
account hijacked 2026-04 2.10.1
A compromised SAP developer account abused trusted publishing, and a static token published mbt, with a pre-install step that ran a credential stealer.
Unpublished within hours of detection.
Source: StepSecurity and Sophos analyses, 29 April 2026. History, not a warning about today — the verdict above is about maintenance now.
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@cap-js/db-service)Watch it
Get told when @cap-js/db-service 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.