@loopback/eslint-confignpm
- latest 17.0.0
- last known licence MIT
- stars 5,101
- assessment attempted today
- GitHub evidence observed yesterday
- registry checked 20 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 →Came back
After 15 months without a release, @loopback/eslint-config published 17.0.0 on 2026-10-24.
Usually this is a maintainer returning. It is also what a hijacked package looks like, so it is worth a glance at what changed before you upgrade.
Maintenance trends
Loading historical repository activity…
Signals · last 21 checks
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node 22 || 24 || 26. Source: the registry.
- Publishers on the registry — 7. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — oct; Oct 2020 (due 2020-10-31) 12/12 done; Dec 2020 (due 2020-12-31); Jan 2021 (due 2021-01-31); Feb 2021 (due 2021-02-28). Source: the repository's milestones.
Third-party facts checked 22 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-10 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@loopback/eslint-config)Watch it
Get told when @loopback/eslint-config 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.