@bitgo/utxo-core
BitGo UTXO Core types
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/paygo/parsePayGoAttestation.js | AI (source-diff): Standard tsc-compiled output; readable business logic visible in sample. | ai | |
| source-diff | obfuscated-file:dist/src/paygo/psbt/payGoAddressProof.js | AI (source-diff): Standard tsc-compiled output; TypeScript boilerplate pattern, not obfuscation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): bitcoinjs-message resolves to BitGo-controlled fork; consistent with org's dependency management pattern. | ai | |
| source-diff | obfuscated-file:dist/src/bip32utils.js | AI (source-diff): Standard tsc-compiled output; long lines from TypeScript boilerplate, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/src/descriptor/parse/PatternMatcher.js | AI (source-diff): Standard tsc-compiled output; readable class implementation in sample. | ai | |
| dependencies | unvetted-dep:@bitgo/unspents | AI (dependencies): Internal BitGo dependency within the same org; consistent across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped BitGo org package; sparse README/no keywords is normal for internal SDK modules. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.39.2 | 6 / 0 | |
| 1.39.1 | 6 / 0 | |
| 1.39.0 | 6 / 0 | |
| 1.38.0 | 6 / 0 | |
| 1.37.1 | 6 / 0 | |
| 1.37.0 | 6 / 0 | |
| 1.36.1 | 6 / 0 | |
| 1.36.0 | 6 / 0 | |
| 1.35.2 | 6 / 0 | |
| 1.23.0 | 7 / 0 | |
| 1.22.0 | 7 / 0 | |
| 1.14.0 | 5 / 0 | |
| 1.13.0 | 5 / 0 | |
| 1.12.0 | 5 / 0 | |
| 1.11.0 | 6 / 1 | |
| 1.10.0 | 6 / 1 | |
| 1.9.1 | 4 / 0 | |
| 1.9.0 | 4 / 0 |
v1.39.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.39.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.39.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.38.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.37.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.37.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.36.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.36.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.35.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.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.
v1.13.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.
v1.12.0
5 findingsThis version was published by a different npm account than previous versions on 2025-07-10. This could indicate a legitimate maintainer transition or an account compromise.
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.
v1.11.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
2 findingsNewly 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.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.