@bitgo/sdk-api
REST wrapper for BitGoJS
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/encryptV2.js | AI (source-diff): Readable new AES-GCM/Argon2 encryption source; long lines from TS boilerplate, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/src/encryptionSession.js | AI (source-diff): Readable new encryption session source; long lines from TS boilerplate, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/hmacStrategy.js | AI (source-diff): Compiled TypeScript test file for HMAC strategy; readable mock/test code. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Previous maintainers replaced by org bot; consistent with BitGo's publishing automation pattern. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change to bitgobot is org-level automation, not an account compromise. | ai | |
| source-diff | obfuscated-file:dist/test/unit/v1/fixtures/accelerate-tx.js | AI (source-diff): Long lines are raw Bitcoin transaction hex in test fixtures, not obfuscation; standard compiled TS test output. | ai | |
| source-diff | obfuscated-file:dist/test/unit/bitgoAPI.js | AI (source-diff): Compiled TypeScript test file; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/test/unit/encrypt.js | AI (source-diff): Compiled TypeScript test file with readable encryption test logic; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/test/unit/utils.js | AI (source-diff): Compiled TypeScript test file with readable utility test logic; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/test/unit/v1/wallet.js | AI (source-diff): Compiled TypeScript wallet test file; long lines are test fixture data, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/test/unit/api.js | AI (source-diff): Compiled TypeScript test file with readable test logic; long lines are standard TS boilerplate. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): bitgobot is BitGo's own automation account with strong approval track record; consolidation under bot publisher is expected for this org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): bitgobot addition is part of BitGo's org-wide publisher consolidation, not a hostile takeover. | ai | |
| phantom-deps | phantom-dep:proxy-agent | AI (phantom-deps): proxy-agent is listed in browser field as false (browser shim exclusion) and declared as a runtime dep; phantom detection is a false positive here. | ai | |
| phantom-deps | phantom-dep:@types/superagent | AI (phantom-deps): @types/superagent is a type declaration package loaded by TypeScript convention, not directly imported at runtime. | ai |
Versions (showing 40 of 140)
| Version | Deps | Published |
|---|---|---|
| 1.56.7 | 16 / 0 | |
| 1.56.6 | 16 / 0 | |
| 1.56.5 | 16 / 0 | |
| 1.56.4 | 16 / 0 | |
| 1.56.3 | 16 / 0 | |
| 1.56.2 | 16 / 0 | |
| 1.56.1 | 16 / 0 | |
| 1.56.0 | 16 / 0 | |
| 1.55.2 | 16 / 0 | |
| 1.55.1 | 16 / 0 | |
| 1.55.0 | 16 / 0 | |
| 1.54.3 | 16 / 0 | |
| 1.54.2 | 16 / 0 | |
| 1.54.1 | 16 / 0 | |
| 1.54.0 | 16 / 0 | |
| 1.53.3 | 16 / 0 | |
| 1.53.2 | 16 / 0 | |
| 1.53.1 | 16 / 0 | |
| 1.53.0 | 16 / 0 | |
| 1.52.0 | 16 / 0 | |
| 1.51.3 | 16 / 0 | |
| 1.51.2 | 16 / 0 | |
| 1.51.1 | 16 / 0 | |
| 1.51.0 | 16 / 0 | |
| 1.50.1 | 16 / 0 | |
| 1.50.0 | 16 / 0 | |
| 1.49.4 | 16 / 0 | |
| 1.49.3 | 16 / 0 | |
| 1.49.2 | 16 / 0 | |
| 1.49.1 | 16 / 0 | |
| 1.49.0 | 16 / 0 | |
| 1.48.1 | 16 / 0 | |
| 1.48.0 | 16 / 0 | |
| 1.47.5 | 16 / 0 | |
| 1.47.4 | 16 / 0 | |
| 1.47.3 | 16 / 0 | |
| 1.47.2 | 16 / 0 | |
| 1.47.1 | 16 / 0 | |
| 1.47.0 | 16 / 0 | |
| 1.46.0 | 16 / 0 |
v1.56.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.