@williamthorsen/strict-lint
Strict linting for ESLint projects
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 6.3.2 | 1 / 0 | |
| 6.3.1 | 1 / 0 | |
| 6.3.0 | 1 / 0 | |
| 6.2.2 | 1 / 0 | |
| 6.2.1 | 1 / 0 | |
| 6.1.2 | 1 / 0 | |
| 6.1.1 | 1 / 0 | |
| 6.1.0 | 1 / 0 | |
| 6.0.0 | 1 / 0 | |
| 5.3.9 | 1 / 0 |
v6.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.