@2digits/eslint-plugin
An eslint plugin that provides a set of rules to enforce best practices for 2digits projects
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 4.0.17 | 4 / 9 | |
| 4.0.16 | 4 / 9 | |
| 4.0.15 | 4 / 9 | |
| 4.0.14 | 4 / 9 | |
| 4.0.13 | 4 / 9 | |
| 4.0.12 | 4 / 9 | |
| 4.0.11 | 4 / 9 | |
| 4.0.10 | 4 / 9 | |
| 4.0.9 | 4 / 9 | |
| 4.0.8 | 4 / 9 | |
| 3.2.9 | 3 / 9 | |
| 3.2.8 | 3 / 9 | |
| 3.2.7 | 3 / 9 | |
| 3.2.6 | 3 / 7 | |
| 3.2.5 | 3 / 7 | |
| 3.2.4 | 3 / 7 | |
| 3.2.3 | 3 / 7 |
v4.0.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.