@bitgo/sdk-coin-eth
BitGo SDK coin library for Ethereum
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/transactionBuilder/decryptionDelegation.js | AI (source-diff): Readable compiled TypeScript test file; long lines are test fixture data, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/decryptionDelegationTxBuilder.js | AI (source-diff): Readable compiled TypeScript test file; long lines are test fixture data, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/src/erc7984Token.js | AI (source-diff): Readable compiled TypeScript source; long lines likely from inline ABI/hex data, not obfuscation. | ai | |
| phantom-deps | phantom-dep:ethereumjs-util | AI (phantom-deps): Declared in package.json dependencies; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:ethers | AI (phantom-deps): Declared in package.json dependencies; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/util | AI (phantom-deps): Declared in package.json dependencies; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:secp256k1 | AI (phantom-deps): Declared in package.json dependencies; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:ethereumjs-abi | AI (phantom-deps): Declared in package.json dependencies; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 25.10.0 | 13 / 3 | |
| 25.9.1 | 13 / 3 | |
| 25.9.0 | 13 / 3 | |
| 25.2.3 | 13 / 3 | |
| 25.2.2 | 13 / 3 | |
| 25.2.1 | 13 / 3 | |
| 25.2.0 | 13 / 3 | |
| 25.1.1 | 13 / 3 | |
| 25.1.0 | 13 / 3 | |
| 25.0.2 | 13 / 3 | |
| 25.0.1 | 13 / 3 | |
| 25.0.0 | 13 / 3 |
v25.10.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v25.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v25.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v25.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.1
2 findingsThis version was published by a different npm account than previous versions on 2025-08-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.