@bitgo/key-card
key card generator for BitGo wallets
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/upgradeWalletEncryption.js | AI (source-diff): Compiled TS build output with descriptive header, not true obfuscation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): fp-ts/io-ts are established, well-vetted FP libraries used across BitGo SDK. | ai | |
| source-diff | obfuscated-file:dist/src/extractKeycardFromPDF.js | AI (source-diff): TypeScript compiler output; long lines from bundled pdfjs-dist content, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/src/parseKeycard.js | AI (source-diff): Readable PDF parsing logic in compiled TS output; long lines are incidental to bundled deps. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Individual BitGo developer accounts replaced by org bot; consistent org-wide pattern. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): BitGo org-wide consolidation to bitgobot CI publisher; consistent across their monorepo packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): bitgobot is BitGo's CI publisher account with 90 approved packages. | ai | |
| provenance | publisher-changed | AI (provenance): pranavjain is an established BitGo org publisher (54 approved); routine maintainer rotation within the org. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established SDK sub-package; sparse README and no keywords are expected for internal monorepo modules. | ai |
Versions (showing 54 of 154)
| Version | Deps | Published |
|---|---|---|
| 0.23.50 | 5 / 1 | |
| 0.23.49 | 5 / 1 | |
| 0.23.48 | 5 / 1 | |
| 0.23.47 | 5 / 1 | |
| 0.23.46 | 5 / 1 | |
| 0.23.45 | 5 / 1 | |
| 0.23.44 | 5 / 1 | |
| 0.23.43 | 5 / 1 | |
| 0.23.42 | 5 / 1 | |
| 0.23.41 | 5 / 1 | |
| 0.23.40 | 5 / 1 | |
| 0.23.38 | 5 / 1 | |
| 0.23.37 | 5 / 1 | |
| 0.23.36 | 5 / 1 | |
| 0.23.35 | 5 / 1 | |
| 0.23.34 | 5 / 1 | |
| 0.23.33 | 5 / 1 | |
| 0.23.32 | 5 / 1 | |
| 0.23.31 | 5 / 1 | |
| 0.23.30 | 5 / 1 | |
| 0.23.29 | 5 / 1 | |
| 0.23.28 | 5 / 1 | |
| 0.23.27 | 5 / 1 | |
| 0.23.26 | 5 / 1 | |
| 0.23.25 | 5 / 1 | |
| 0.23.24 | 5 / 1 | |
| 0.23.23 | 5 / 1 | |
| 0.23.22 | 5 / 1 | |
| 0.23.21 | 5 / 1 | |
| 0.23.20 | 5 / 1 | |
| 0.23.19 | 5 / 1 | |
| 0.23.18 | 5 / 1 | |
| 0.23.17 | 5 / 1 | |
| 0.23.16 | 5 / 1 | |
| 0.23.15 | 5 / 1 | |
| 0.23.14 | 5 / 1 | |
| 0.23.13 | 5 / 1 | |
| 0.23.12 | 5 / 1 | |
| 0.23.11 | 5 / 1 | |
| 0.23.10 | 5 / 1 | |
| 0.23.9 | 5 / 1 | |
| 0.23.8 | 5 / 1 | |
| 0.23.7 | 5 / 1 | |
| 0.23.6 | 5 / 1 | |
| 0.23.5 | 5 / 1 | |
| 0.23.4 | 5 / 1 | |
| 0.23.3 | 5 / 1 | |
| 0.23.2 | 5 / 1 | |
| 0.23.1 | 5 / 1 | |
| 0.23.0 | 5 / 1 | |
| 0.22.18 | 5 / 1 | |
| 0.22.17 | 5 / 1 | |
| 0.22.16 | 5 / 1 | |
| 0.22.15 | 5 / 1 |
v0.23.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.