@dfns/lib-ethersjs6
Supply chain provenance
Status for the latest visible version.
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.8.21 | 2 / 0 | |
| 0.8.20 | 2 / 0 | |
| 0.8.19 | 2 / 0 | |
| 0.8.18 | 2 / 0 | |
| 0.8.17 | 2 / 0 | |
| 0.8.9 | 2 / 0 | |
| 0.8.7 | 2 / 0 | |
| 0.8.6 | 2 / 0 | |
| 0.8.4 | 2 / 0 | |
| 0.8.3 | 2 / 0 | |
| 0.8.2 | 2 / 0 | |
| 0.7.18 | 0 / 0 | |
| 0.7.0 | 0 / 0 |
v0.8.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.