@riverqueue/driver-pgnpm
- latest 0.3.2
- last known licence MPL-2.0
- stars 5,885
- assessment attempted yesterday
- GitHub evidence observed yesterday
- registry checked 15 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 8 checks
Commits 90d
100
Open issues
31
Unanswered
0
Contributors
9
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 — 1. Source: the registry.
- OpenSSF Scorecard — 5.9 / 10 on 2026-08-24. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.
Third-party facts checked 11 days ago; registry facts on every crawl.
State history 2
| When | Change |
|---|---|
| 2026-11-11 | unknown → active |
| 2026-09-30 | first verdict: unknown |
Licence history 1
| When | Change | Severity |
|---|---|---|
| 2026-10-28 | LGPL-3.0-or-later → MPL-2.0 (0.3.0) | info |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@riverqueue/driver-pg)Watch it
Get told when @riverqueue/driver-pg 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.