@dfns/lib-ethersjs5
Supply chain provenance
Status for the latest visible version.
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Declared in dependencies; used transitively via ethersproject packages. | ai | |
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): Declared in dependencies; used transitively via ethersproject packages. | ai | |
| phantom-deps | phantom-dep:cross-fetch | AI (phantom-deps): Declared in dependencies; used transitively via ethersproject packages. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.8.21 | 12 / 0 | |
| 0.8.20 | 12 / 0 | |
| 0.8.19 | 12 / 0 | |
| 0.8.18 | 12 / 0 | |
| 0.8.17 | 12 / 0 | |
| 0.8.13 | 12 / 0 | |
| 0.8.12 | 12 / 0 | |
| 0.8.11 | 12 / 0 | |
| 0.8.10 | 12 / 0 | |
| 0.8.9 | 12 / 0 | |
| 0.8.7 | 12 / 0 | |
| 0.8.6 | 12 / 0 | |
| 0.8.4 | 12 / 0 | |
| 0.8.3 | 12 / 0 | |
| 0.8.2 | 12 / 0 | |
| 0.7.18 | 10 / 0 | |
| 0.7.0 | 10 / 0 | |
| 0.6.12 | 13 / 0 | |
| 0.6.11 | 13 / 0 | |
| 0.6.10 | 13 / 0 | |
| 0.6.9 | 13 / 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.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v0.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.