@azure/logger-jsnpm
- latest 1.3.2
- last known licence MIT
- stars 7
- assessment attempted 5 days ago
- GitHub evidence observed 5 days ago
- registry checked 16 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 2 checks
Commits 90d
0
Open issues
0
Unanswered
0
Contributors
0
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Publishers on the registry — 3. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — Sprint-133 (due 2019-04-08) 1/1 done; Sprint-134 (due 2019-04-29); Sprint-135 (due 2019-05-20); Sprint-136 (due 2019-06-10). Source: the repository's milestones.
- OpenSSF Scorecard — 3.6 / 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 5 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-01 | first verdict: abandoned |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@azure/logger-js)Watch it
Get told when @azure/logger-js 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.