@bitgo-beta/utxo-core
BitGo UTXO Core types
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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/descriptor/derive.js | AI (source-diff): Standard tsc-compiled output; long lines from TS boilerplate, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/src/dustThreshold.js | AI (source-diff): Standard tsc-compiled output; long lines from TS boilerplate, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/src/Output.js | AI (source-diff): Standard tsc-compiled output; long lines from TS boilerplate, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/src/descriptor/psbt/sign.js | AI (source-diff): Standard tsc-compiled output; long lines from TS boilerplate, not obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): BitGo SDK monorepo package; sparse README/keywords are typical for internal SDK modules. | ai |
v1.8.0
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.