@abp/lodashnpm
- latest 10.7.1
- last known licence LGPL-3.0
- stars 14,467
- assessment attempted yesterday
- GitHub evidence observed yesterday
- registry checked 9 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 6 checks
Commits 90d
100
Open issues
289
Unanswered
125
Contributors
12
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Publishers on the registry — 2. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — backlog 0/265 done; 10.6-patch (due 2026-08-18) 21/21 done; 10.7-final (due 2026-08-18) 94/96 done; 10.8-preview (due 2026-09-01) 44/48 done. Source: the repository's milestones.
- OpenSSF Scorecard — 6.1 / 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 yesterday; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-05 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@abp/lodash)Watch it
Get told when @abp/lodash 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.