@leanup/cli-core-babelnpm
- latest 1.3.54
- last known licence Apache-2.0
- stars 34
- assessment attempted 16 days ago
- GitHub evidence observed 16 days ago
- registry checked 17 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
31
Unanswered
25
Contributors
0
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.
- Open milestones — Release v1.1 (due 2020-12-24) 23/24 done; Release v1.2 (due 2021-01-31) 8/9 done. Source: the repository's milestones.
- OpenSSF Scorecard — 3.7 / 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 16 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-27 | first verdict: finished |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@leanup/cli-core-babel)Watch it
Get told when @leanup/cli-core-babel 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.