@bitgo/sdk-coin-opeth
BitGo SDK coin library for Optimism
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): bitgobot is BitGo's established CI bot account; consolidation to automation is expected. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of individual BitGo employee accounts in favor of CI bot is consistent org-wide pattern. | ai | |
| source-diff | obfuscated-file:dist/test/fixtures/opeth.js | AI (source-diff): Compiled test fixture with readable BitGo-specific test data; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/test/unit/opeth.js | AI (source-diff): TypeScript-compiled test file with standard TS boilerplate; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/test/unit/opethToken.js | AI (source-diff): TypeScript-compiled test file with readable BitGo test logic; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/test/resources.js | AI (source-diff): Compiled test resources with readable constants and hex-encoded tx data; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/send.js | AI (source-diff): TypeScript-compiled test file with standard TS boilerplate; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/addressInitialization.js | AI (source-diff): TypeScript-compiled test file with standard TS boilerplate; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/test/resources.d.ts | AI (source-diff): TypeScript declaration file for test resources; long lines from exported constant names, not obfuscation. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): BitGo migrated to CI/CD publishing (bitgobot/louib-bitgo) with SLSA provenance; consistent with org-wide automation transition. | ai | |
| provenance | publisher-changed | AI (provenance): GitHub Actions publisher with SLSA attestation is the expected pattern for BitGo's automated release pipeline. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transaction.js | AI (source-diff): TypeScript-compiled test file with standard TS boilerplate; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transferBuilder.js | AI (source-diff): TypeScript-compiled test file with standard TS boilerplate; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/test/unit/transactionBuilder/walletInitialization.js | AI (source-diff): TypeScript-compiled test file with standard TS boilerplate; not obfuscated. | ai | |
| phantom-deps | phantom-dep:ethereumjs-abi | AI (phantom-deps): Declared as runtime dep; referenced in config files is expected for this Ethereum coin library. | ai | |
| phantom-deps | phantom-dep:@bitgo/secp256k1 | AI (phantom-deps): Same-org scoped package; stable false positive for BitGo SDK packages. | ai | |
| phantom-deps | phantom-dep:ethereumjs-util | AI (phantom-deps): Declared as runtime dep; phantom-dep heuristic false positive for this Ethereum coin library. | ai |
Versions (showing 53 of 153)
| Version | Deps | Published |
|---|---|---|
| 18.1.49 | 7 / 3 | |
| 18.1.48 | 7 / 3 | |
| 18.1.47 | 7 / 3 | |
| 18.1.45 | 7 / 3 | |
| 18.1.44 | 7 / 3 | |
| 18.1.43 | 7 / 3 | |
| 18.1.42 | 7 / 3 | |
| 18.1.41 | 7 / 3 | |
| 18.1.40 | 7 / 3 | |
| 18.1.39 | 7 / 3 | |
| 18.1.37 | 7 / 3 | |
| 18.1.36 | 7 / 3 | |
| 18.1.35 | 7 / 3 | |
| 18.1.34 | 7 / 3 | |
| 18.1.33 | 7 / 3 | |
| 18.1.32 | 7 / 3 | |
| 18.1.31 | 7 / 3 | |
| 18.1.30 | 7 / 3 | |
| 18.1.29 | 7 / 3 | |
| 18.1.28 | 7 / 3 | |
| 18.1.27 | 7 / 3 | |
| 18.1.26 | 7 / 3 | |
| 18.1.25 | 7 / 3 | |
| 18.1.24 | 7 / 3 | |
| 18.1.23 | 7 / 3 | |
| 18.1.22 | 7 / 3 | |
| 18.1.21 | 7 / 3 | |
| 18.1.20 | 7 / 3 | |
| 18.1.19 | 7 / 3 | |
| 18.1.18 | 7 / 3 | |
| 18.1.17 | 7 / 3 | |
| 18.1.16 | 7 / 3 | |
| 18.1.15 | 7 / 3 | |
| 18.1.14 | 7 / 3 | |
| 18.1.13 | 7 / 3 | |
| 18.1.12 | 7 / 3 | |
| 18.1.11 | 7 / 3 | |
| 18.1.10 | 7 / 3 | |
| 18.1.9 | 7 / 3 | |
| 18.1.8 | 7 / 3 | |
| 18.1.7 | 7 / 3 | |
| 18.1.6 | 7 / 3 | |
| 18.1.5 | 7 / 3 | |
| 18.1.4 | 7 / 3 | |
| 18.1.3 | 7 / 3 | |
| 18.1.2 | 7 / 3 | |
| 18.1.1 | 7 / 3 | |
| 18.1.0 | 7 / 3 | |
| 18.0.6 | 7 / 3 | |
| 18.0.5 | 7 / 3 | |
| 18.0.4 | 7 / 3 | |
| 18.0.3 | 7 / 3 | |
| 18.0.2 | 7 / 3 |
v18.1.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.