@willbooster/eslint-config-next
ESLint flat config for Next.js projects
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 3.0.4 | 0 / 13 | |
| 3.0.3 | 0 / 13 | |
| 3.0.2 | 0 / 15 | |
| 3.0.1 | 0 / 34 | |
| 3.0.0 | 0 / 30 | |
| 2.6.2 | 0 / 30 | |
| 2.6.1 | 0 / 31 | |
| 2.6.0 | 0 / 31 | |
| 2.5.15 | 0 / 31 | |
| 2.5.14 | 0 / 31 | |
| 2.5.13 | 0 / 31 | |
| 2.5.12 | 0 / 31 |
v3.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.