@bitgo/abstract-eth
BitGo SDK coin library for ETH base implementation
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/src/lib/messages/eip191/eip191MessageBuilder.js | AI (source-diff): Compiled TypeScript source file; long lines from source maps, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/messages/eip191/eip191Message.js | AI (source-diff): Compiled TypeScript test file; long lines from test fixture data, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/messages/messageBuilderFactory.js | AI (source-diff): Compiled TypeScript test file; long lines from test fixture data, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/messages/eip191/eip191MessageBuilder.js | AI (source-diff): Compiled TypeScript test file; long lines from test fixture data, not obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): New publisher zahin-mohammad has strong BitGo track record (321/0); consistent with internal team rotation. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Same monorepo pattern; stable FP. | ai | |
| phantom-deps | phantom-dep:secp256k1 | AI (phantom-deps): Same monorepo pattern; stable FP. | ai | |
| phantom-deps | phantom-dep:superagent | AI (phantom-deps): Same monorepo pattern; stable FP. | ai | |
| phantom-deps | phantom-dep:bignumber.js | AI (phantom-deps): Same monorepo pattern; stable FP. | ai | |
| phantom-deps | phantom-dep:@bitgo/statics | AI (phantom-deps): Same org scope; stable FP. | ai | |
| phantom-deps | phantom-dep:bn.js | AI (phantom-deps): Monorepo TypeScript package; phantom-dep heuristic fires on config-referenced deps, stable FP for this package. | ai | |
| phantom-deps | phantom-dep:debug | AI (phantom-deps): Same monorepo pattern; stable FP. | ai | |
| phantom-deps | phantom-dep:ethers | AI (phantom-deps): Same monorepo pattern; stable FP. | ai | |
| phantom-deps | phantom-dep:keccak | AI (phantom-deps): Same monorepo pattern; stable FP. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/rlp | AI (phantom-deps): Same monorepo pattern; stable FP. | ai | |
| phantom-deps | phantom-dep:ethereumjs-util | AI (phantom-deps): Same monorepo pattern; stable FP. | ai | |
| phantom-deps | phantom-dep:@bitgo/secp256k1 | AI (phantom-deps): Same org scope; stable FP. | ai | |
| phantom-deps | phantom-dep:@bitgo/sdk-lib-mpc | AI (phantom-deps): Same org scope; stable FP. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/common | AI (phantom-deps): Same monorepo pattern; stable FP. | ai | |
| phantom-deps | phantom-dep:@metamask/eth-sig-util | AI (phantom-deps): Same monorepo pattern; stable FP. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/tx | AI (phantom-deps): Same monorepo pattern; stable FP. | ai | |
| phantom-deps | phantom-dep:ethereumjs-abi | AI (phantom-deps): Same monorepo pattern; stable FP. | ai | |
| phantom-deps | phantom-dep:@bitgo/sdk-core | AI (phantom-deps): Same org scope; stable FP. | ai | |
| source-diff | obfuscated-file:dist/src/lib/zamaUtils.js | AI (source-diff): Compiled TypeScript utility; long lines from ABI method ID computation, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/decryptionDelegationBuilder.js | AI (source-diff): Compiled TypeScript test file; long lines from ABI hex constants, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/src/lib/decryptionDelegationBuilder.js | AI (source-diff): Compiled TypeScript source; long lines from ABI encoding, fully readable logic. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/decryptionDelegation.js | AI (source-diff): Compiled TypeScript test file; long lines from ABI hex constants, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/zamaUtils.js | AI (source-diff): Compiled TypeScript test file; long lines from ABI hex constants, not obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal SDK module; sparse README and no keywords are expected for a monorepo sub-package. | ai |
Versions (showing 51 of 75)
| Version | Deps | Published |
|---|---|---|
| 24.27.1 | 18 / 3 | |
| 24.27.0 | 18 / 3 | |
| 24.26.1 | 18 / 3 | |
| 24.26.0 | 18 / 3 | |
| 24.25.1 | 18 / 3 | |
| 24.25.0 | 18 / 3 | |
| 24.24.3 | 18 / 3 | |
| 24.24.2 | 18 / 3 | |
| 24.24.1 | 18 / 3 | |
| 24.24.0 | 18 / 3 | |
| 24.23.1 | 18 / 3 | |
| 24.23.0 | 18 / 3 | |
| 24.22.1 | 18 / 3 | |
| 24.22.0 | 18 / 3 | |
| 24.21.0 | 18 / 3 | |
| 24.20.8 | 18 / 3 | |
| 24.20.7 | 18 / 3 | |
| 24.20.6 | 18 / 3 | |
| 24.20.5 | 18 / 3 | |
| 24.20.4 | 18 / 3 | |
| 24.20.3 | 18 / 3 | |
| 24.20.2 | 18 / 3 | |
| 24.20.1 | 18 / 3 | |
| 24.20.0 | 18 / 3 | |
| 24.19.8 | 18 / 3 | |
| 24.19.6 | 18 / 3 | |
| 24.19.5 | 18 / 3 | |
| 24.19.4 | 18 / 3 | |
| 24.19.3 | 18 / 3 | |
| 24.19.2 | 18 / 3 | |
| 24.19.1 | 18 / 3 | |
| 24.19.0 | 18 / 3 | |
| 24.18.0 | 18 / 3 | |
| 24.17.0 | 18 / 3 | |
| 24.16.0 | 18 / 3 | |
| 24.15.0 | 18 / 3 | |
| 24.14.3 | 18 / 3 | |
| 24.14.2 | 18 / 3 | |
| 24.14.1 | 18 / 3 | |
| 24.14.0 | 18 / 3 | |
| 24.13.7 | 18 / 3 | |
| 24.13.6 | 18 / 3 | |
| 24.13.5 | 18 / 3 | |
| 24.13.4 | 18 / 3 | |
| 24.13.3 | 18 / 3 | |
| 24.13.2 | 18 / 3 | |
| 24.13.1 | 18 / 3 | |
| 24.13.0 | 18 / 3 | |
| 24.12.0 | 18 / 3 | |
| 24.11.3 | 18 / 3 | |
| 24.11.2 | 18 / 3 |
v24.27.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v24.27.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v24.26.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v24.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v24.25.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v24.25.0
6 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.
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.
v24.24.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v24.24.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v24.24.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v24.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v24.23.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v24.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v24.22.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v24.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v24.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v24.20.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v24.20.7
2 findingsThis version was published by a different npm account than previous versions on 2026-03-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v24.20.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.20.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.19.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.19.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.19.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.13.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.11.3
2 findingsThis version was published by a different npm account than previous versions on 2025-08-30. 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.
v24.11.2
2 findingsThis version was published by a different npm account than previous versions on 2025-08-29. 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.