@willbooster/eslint-config-ts-react
ESLint flat config for TypeScript React projects
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; consistent with org-level CI migration for WillBooster packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation confirms legitimate CI publish; dormancy explained by infrequent release cadence for this config package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 12.1.4 | 0 / 12 | |
| 12.1.3 | 0 / 11 | |
| 12.1.2 | 0 / 13 | |
| 12.1.1 | 0 / 32 | |
| 12.1.0 | 0 / 28 | |
| 12.0.0 | 0 / 28 | |
| 11.6.1 | 2 / 28 | |
| 11.6.0 | 2 / 28 | |
| 11.5.15 | 2 / 28 | |
| 11.5.14 | 2 / 28 | |
| 11.5.13 | 2 / 28 | |
| 11.5.12 | 2 / 28 |
v12.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v12.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.6.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.5.15
2 findingsThis version was published by a different npm account than previous versions on 2026-03-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.5.14
2 findingsThis version was published by a different npm account than previous versions on 2025-12-13. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.5.13
2 findingsThis version was published by a different npm account than previous versions on 2025-12-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.