@uma/loggernpm
- latest 1.3.3
- licence AGPL-3.0-or-later
- stars 485
- checked 3 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
5
Unanswered
4
Contributors
9
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Publishers on the registry — 4. Source: the registry.
- Open milestones — Technical Debt 35/35 done; Oracle v1 65/65 done; Sponsor dApp V2 26/26 done; Voting CLI 7/7 done; Sponsor CLI 7/7 done. Source: the repository's milestones.
- OpenSSF Scorecard — 4.2 / 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 3 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-09-16 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@uma/logger)Watch it
Get told when @uma/logger 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.