@payloadcms/eslint-confignpm
- latest 3.28.0
- last known licence MIT
- stars 45,757
- assessment attempted yesterday
- GitHub evidence observed yesterday
- registry checked 19 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 12 checks
Commits 90d
100
Open issues
592
Unanswered
160
Contributors
24
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Publishers on the registry — 13. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — v3.0 7/7 done; v3.1 4/4 done. Source: the repository's milestones.
- OpenSSF Scorecard — 4.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 11 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/@payloadcms/eslint-config)Watch it
Get told when @payloadcms/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.