@bitgo/sdk-lib-mpc
library functions for BitGo's MPC solution
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/tss/eddsa-mps/derive.js | AI (source-diff): Readable compiled TS with long comment lines; not obfuscated. Stable pattern for this package's dist output. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of individual maintainers in favor of bitgobot is a known BitGo org-wide consolidation. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): BitGo consolidated all package publishing under bitgobot automation account; not a hostile takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): bitgobot is BitGo's org-wide automation publisher; addition is expected. | ai | |
| source-diff | obfuscated-file:dist/src/tss/eddsa-mps/types.js | AI (source-diff): TypeScript-compiled CJS output; long lines are TS boilerplate helpers, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/src/tss/eddsa-mps/commsLayer.js | AI (source-diff): TypeScript-compiled CJS output; long lines are TS boilerplate helpers, not obfuscation. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/src/tss/eddsa-mps/dkg.js | AI (source-diff): TypeScript-compiled CJS output with readable DKG class and comments; not obfuscated. | ai | |
| provenance | publisher-changed | AI (provenance): bitgobot is BitGo's org publishing account with 333 approved packages; publisher transition is organizational, not a takeover. | ai | |
| phantom-deps | phantom-dep:@types/superagent | AI (phantom-deps): Type-only dependency; not imported at runtime, stable false positive for this package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 10.15.0 | 15 / 6 | |
| 10.14.1 | 15 / 6 | |
| 10.14.0 | 15 / 6 | |
| 10.13.0 | 15 / 6 | |
| 10.12.0 | 15 / 6 | |
| 10.11.1 | 15 / 6 | |
| 10.11.0 | 15 / 6 | |
| 10.10.2 | 14 / 6 | |
| 10.10.1 | 14 / 6 | |
| 10.10.0 | 14 / 6 | |
| 10.9.0 | 14 / 7 | |
| 10.8.1 | 14 / 7 | |
| 10.8.0 | 14 / 7 | |
| 10.7.0 | 14 / 7 | |
| 10.6.0 | 14 / 7 | |
| 10.5.0 | 14 / 7 | |
| 10.4.0 | 14 / 7 | |
| 10.3.0 | 14 / 7 | |
| 10.2.0 | 14 / 7 | |
| 10.1.2 | 14 / 7 | |
| 10.1.1 | 14 / 7 | |
| 10.1.0 | 14 / 7 | |
| 10.0.1 | 14 / 7 | |
| 10.0.0 | 14 / 7 |
v10.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.2.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 (mohammadalfaiyaz_bitgo) than the most recent previously approved version (margueriteblair) 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.
v10.1.2
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 2025-03-04, 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.
v10.1.1
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 2025-02-25, 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.
v10.1.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 (pengyuc_bitgo) on 2024-11-01, 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.
v10.0.1
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 (pengyuc_bitgo) on 2024-10-22, 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.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.