@bitgo/utxo-staking
BitGo SDK for build UTXO staking transactions
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-takeover | AI (maintainer-change): bitgobot is BitGo's trusted CI publisher account, org-wide migration. | ai | |
| source-diff | obfuscated-file:dist/cjs/scripts/babylon-sync.js | AI (source-diff): tsc-compiled CJS boilerplate, not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/src/babylon/stakingManager.js | AI (source-diff): Compiled tsc dist output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/src/babylon/parseDescriptor.js | AI (source-diff): Compiled TS output from BitGo monorepo, not obfuscation; readable code in sample. | ai | |
| source-diff | obfuscated-file:dist/src/babylon/undelegation/unbonding.js | AI (source-diff): Compiled TS output with standard tsc helper boilerplate, not obfuscation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Internal BitGo maintainer roster change, no behavior change in package. | ai | |
| provenance | publisher-changed | AI (provenance): bitgobot is BitGo's trusted publishing bot with strong track record; org-managed rotation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Internal BitGo maintainer roster change, no behavior change in package. | ai | |
| source-diff | obfuscated-file:dist/src/babylon/stakingParams.js | AI (source-diff): Plain staking-param constants, minified formatting only. | ai | |
| source-diff | obfuscated-file:dist/src/babylon/delegationMessage.js | AI (source-diff): Compiled TS dist output with tsc helpers, not true obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): BitGo SDK sub-package; sparse README/no keywords is a consistent pattern across the monorepo, not a spam signal. | ai |
Versions (showing 57 of 57)
| Version | Deps | Published |
|---|---|---|
| 1.41.5 | 11 / 1 | |
| 1.41.4 | 11 / 1 | |
| 1.41.3 | 11 / 1 | |
| 1.41.2 | 11 / 1 | |
| 1.41.1 | 11 / 1 | |
| 1.41.0 | 11 / 1 | |
| 1.40.0 | 11 / 1 | |
| 1.39.0 | 11 / 1 | |
| 1.38.1 | 11 / 1 | |
| 1.31.0 | 11 / 1 | |
| 1.25.0 | 11 / 1 | |
| 1.24.0 | 11 / 1 | |
| 1.23.3 | 11 / 1 | |
| 1.23.2 | 11 / 1 | |
| 1.23.1 | 11 / 1 | |
| 1.23.0 | 11 / 1 | |
| 1.22.4 | 11 / 1 | |
| 1.22.3 | 11 / 1 | |
| 1.22.2 | 11 / 1 | |
| 1.22.1 | 11 / 1 | |
| 1.22.0 | 11 / 1 | |
| 1.21.3 | 11 / 1 | |
| 1.21.2 | 11 / 1 | |
| 1.21.1 | 11 / 1 | |
| 1.21.0 | 11 / 1 | |
| 1.20.4 | 11 / 1 | |
| 1.20.3 | 11 / 1 | |
| 1.20.2 | 11 / 1 | |
| 1.20.1 | 11 / 1 | |
| 1.20.0 | 11 / 1 | |
| 1.19.0 | 11 / 1 | |
| 1.18.1 | 10 / 1 | |
| 1.18.0 | 10 / 1 | |
| 1.17.0 | 11 / 1 | |
| 1.16.3 | 11 / 1 | |
| 1.16.2 | 11 / 1 | |
| 1.16.1 | 11 / 1 | |
| 1.16.0 | 11 / 1 | |
| 1.15.0 | 11 / 1 | |
| 1.14.0 | 11 / 1 | |
| 1.13.0 | 10 / 1 | |
| 1.12.1 | 10 / 1 | |
| 1.12.0 | 10 / 1 | |
| 1.11.0 | 10 / 1 | |
| 1.10.0 | 7 / 0 | |
| 1.9.0 | 4 / 2 | |
| 1.8.0 | 4 / 2 | |
| 1.7.0 | 4 / 2 | |
| 1.6.1 | 4 / 2 | |
| 1.5.0 | 3 / 0 | |
| 1.3.5 | 3 / 0 | |
| 1.3.4 | 3 / 0 | |
| 1.3.3 | 3 / 0 | |
| 1.3.2 | 3 / 0 | |
| 1.3.1 | 3 / 0 | |
| 1.3.0 | 3 / 0 | |
| 1.2.0 | 3 / 0 |
v1.41.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.41.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.41.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.20.3
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (zahin-mohammad) than the most recent previously approved version (pranavjain) on 2025-08-19, but zahin-mohammad is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.20.2
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (zahin-mohammad) than the most recent previously approved version (pranavjain) on 2025-08-14, but zahin-mohammad is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.20.1
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mohammadalfaiyaz_bitgo) than the most recent previously approved version (pranavjain) on 2025-08-07, but mohammadalfaiyaz_bitgo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.20.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mohammadalfaiyaz_bitgo) than the most recent previously approved version (pranavjain) on 2025-07-25, but mohammadalfaiyaz_bitgo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.19.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mohammadalfaiyaz_bitgo) than the most recent previously approved version (pranavjain) on 2025-07-23, but mohammadalfaiyaz_bitgo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mohammadalfaiyaz_bitgo) than the most recent previously approved version (alebusse) on 2025-04-25, but mohammadalfaiyaz_bitgo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pranavjain) than the most recent previously approved version (alebusse) on 2025-04-15, but pranavjain is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.12.1
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mohammadalfaiyaz_bitgo) than the most recent previously approved version (alebusse) on 2025-04-04, but mohammadalfaiyaz_bitgo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.12.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mohammadalfaiyaz_bitgo) than the most recent previously approved version (alebusse) on 2025-03-28, but mohammadalfaiyaz_bitgo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.11.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pranavjain) than the most recent previously approved version (alebusse) on 2025-03-20, but pranavjain is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pranavjain) than the most recent previously approved version (alebusse) on 2025-03-18, but pranavjain is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.9.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alebusse) than the most recent previously approved version (margueriteblair) on 2025-03-06, but alebusse is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (margueriteblair) than the most recent previously approved version (alebusse) on 2024-12-12, but margueriteblair is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.3.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alebusse) than the most recent previously approved version (margueriteblair) on 2024-12-11, but alebusse is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.