@bitgo/sdk-coin-ethw
BitGo SDK coin library for Ethereum pow
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/test/unit/index.js | AI (source-diff): TypeScript compiled test file with long nock fixture lines; not obfuscated, stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/test/lib/recovery-nocks.js | AI (source-diff): Compiled nock fixture data with long JSON lines; not obfuscated, stable pattern for this package. | ai | |
| provenance | publisher-changed | AI (provenance): New publisher mohammadalfaiyaz_bitgo is an established BitGo team account with 63 approved packages; consistent with internal maintainer rotation. | ai | |
| provenance | no-provenance | AI (provenance): BitGo SDK packages consistently lack Sigstore provenance; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@bitgo/sdk-core | AI (dependencies): Internal BitGo monorepo dependency; expected and stable for this package family. | ai | |
| dependencies | unvetted-dep:@bitgo/sdk-coin-eth | AI (dependencies): Internal BitGo monorepo dependency; expected and stable for this package family. | ai |
Versions (showing 100 of 153)
| Version | Deps | Published |
|---|---|---|
| 20.5.26 | 5 / 2 | |
| 20.5.25 | 5 / 2 | |
| 20.5.23 | 5 / 2 | |
| 20.5.22 | 5 / 2 | |
| 20.5.21 | 5 / 2 | |
| 20.5.20 | 5 / 2 | |
| 20.5.19 | 5 / 2 | |
| 20.5.18 | 5 / 2 | |
| 20.5.17 | 5 / 2 | |
| 20.5.16 | 5 / 2 | |
| 20.5.15 | 5 / 2 | |
| 20.5.14 | 5 / 2 | |
| 20.5.13 | 5 / 2 | |
| 20.5.12 | 5 / 2 | |
| 20.5.11 | 5 / 2 | |
| 20.5.10 | 5 / 2 | |
| 20.5.9 | 5 / 2 | |
| 20.5.8 | 5 / 2 | |
| 20.5.7 | 5 / 2 | |
| 20.5.6 | 5 / 2 | |
| 20.5.5 | 5 / 2 | |
| 20.5.4 | 5 / 2 | |
| 20.5.3 | 5 / 2 | |
| 20.5.2 | 5 / 2 | |
| 20.5.1 | 5 / 2 | |
| 20.5.0 | 5 / 2 | |
| 20.4.9 | 5 / 2 | |
| 20.4.8 | 5 / 2 | |
| 20.4.7 | 5 / 2 | |
| 20.4.6 | 5 / 2 | |
| 20.4.5 | 5 / 2 | |
| 20.4.4 | 5 / 2 | |
| 20.4.3 | 5 / 2 | |
| 20.4.2 | 5 / 2 | |
| 20.4.1 | 5 / 2 | |
| 20.4.0 | 5 / 2 | |
| 20.3.24 | 5 / 2 | |
| 20.3.22 | 5 / 2 | |
| 20.3.21 | 5 / 2 | |
| 20.3.20 | 5 / 2 | |
| 20.3.19 | 5 / 2 | |
| 20.3.18 | 5 / 2 | |
| 20.3.17 | 5 / 2 | |
| 20.3.16 | 5 / 2 | |
| 20.3.15 | 5 / 2 | |
| 20.3.14 | 5 / 2 | |
| 20.3.13 | 5 / 2 | |
| 20.3.12 | 5 / 2 | |
| 20.3.11 | 5 / 2 | |
| 20.3.10 | 5 / 2 | |
| 20.3.9 | 5 / 2 | |
| 20.3.8 | 5 / 2 | |
| 20.3.7 | 5 / 2 | |
| 20.3.6 | 5 / 2 | |
| 20.3.5 | 5 / 2 | |
| 20.3.4 | 5 / 2 | |
| 20.3.3 | 5 / 2 | |
| 20.3.2 | 5 / 2 | |
| 20.3.1 | 5 / 2 | |
| 20.3.0 | 5 / 2 | |
| 20.2.4 | 5 / 2 | |
| 20.2.3 | 5 / 2 | |
| 20.2.2 | 5 / 2 | |
| 20.2.1 | 5 / 2 | |
| 20.2.0 | 5 / 2 | |
| 20.1.15 | 5 / 2 | |
| 20.1.14 | 5 / 2 | |
| 20.1.13 | 5 / 2 | |
| 20.1.12 | 5 / 2 | |
| 20.1.11 | 5 / 2 | |
| 20.1.10 | 5 / 2 | |
| 20.1.9 | 5 / 2 | |
| 20.1.8 | 5 / 2 | |
| 20.1.7 | 5 / 2 | |
| 20.1.6 | 5 / 2 | |
| 20.1.5 | 5 / 2 | |
| 20.1.4 | 5 / 2 | |
| 20.1.3 | 5 / 2 | |
| 20.1.2 | 5 / 2 | |
| 20.1.1 | 5 / 2 | |
| 20.1.0 | 5 / 2 | |
| 20.0.83 | 5 / 2 | |
| 20.0.82 | 5 / 2 | |
| 20.0.81 | 5 / 2 | |
| 20.0.80 | 5 / 2 | |
| 20.0.79 | 5 / 2 | |
| 20.0.78 | 5 / 2 | |
| 20.0.77 | 5 / 2 | |
| 20.0.76 | 5 / 2 | |
| 20.0.75 | 5 / 2 | |
| 20.0.74 | 5 / 2 | |
| 20.0.73 | 5 / 2 | |
| 20.0.72 | 5 / 2 | |
| 20.0.71 | 5 / 2 | |
| 20.0.70 | 5 / 2 | |
| 20.0.69 | 5 / 2 | |
| 20.0.68 | 5 / 2 | |
| 20.0.67 | 5 / 2 | |
| 20.0.66 | 5 / 2 | |
| 20.0.65 | 5 / 2 |
v20.5.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v20.5.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v20.5.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v20.5.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v20.5.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v20.5.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v20.0.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.