@bitgo/public-types
Collection of types exposed externally as part of the BitGo public API
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): BitGo migrated publishing from bitgobot to GitHub Actions CI; consistent across org packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal type-definition package; sparse README and no keywords are expected for this use case. | ai | |
| phantom-deps | phantom-dep:monocle-ts | AI (phantom-deps): fp-ts ecosystem dep likely re-exported as part of public types API rather than directly imported. | ai | |
| phantom-deps | phantom-dep:newtype-ts | AI (phantom-deps): fp-ts ecosystem dep likely re-exported as part of public types API rather than directly imported. | ai |
Versions (showing 51 of 98)
| Version | Deps | Published |
|---|---|---|
| 6.27.0 | 5 / 5 | |
| 6.26.0 | 5 / 5 | |
| 6.25.0 | 5 / 5 | |
| 6.24.0 | 5 / 5 | |
| 6.23.0 | 5 / 5 | |
| 6.22.0 | 5 / 5 | |
| 6.21.0 | 5 / 5 | |
| 6.20.0 | 5 / 5 | |
| 6.19.0 | 5 / 5 | |
| 6.18.0 | 5 / 5 | |
| 6.17.0 | 5 / 5 | |
| 6.16.0 | 5 / 5 | |
| 6.15.0 | 5 / 5 | |
| 6.14.0 | 5 / 5 | |
| 6.13.0 | 5 / 5 | |
| 6.12.0 | 5 / 5 | |
| 6.11.0 | 5 / 5 | |
| 6.10.0 | 5 / 5 | |
| 6.9.0 | 5 / 5 | |
| 6.8.1 | 5 / 5 | |
| 6.8.0 | 5 / 5 | |
| 6.7.0 | 5 / 5 | |
| 6.6.0 | 5 / 5 | |
| 6.5.2 | 5 / 5 | |
| 6.5.1 | 5 / 5 | |
| 6.5.0 | 5 / 5 | |
| 6.4.0 | 5 / 5 | |
| 6.3.0 | 5 / 5 | |
| 6.2.0 | 5 / 5 | |
| 6.1.0 | 5 / 5 | |
| 6.0.0 | 5 / 5 | |
| 5.97.0 | 5 / 5 | |
| 5.96.2 | 5 / 5 | |
| 5.96.1 | 5 / 5 | |
| 5.96.0 | 5 / 5 | |
| 5.95.0 | 5 / 5 | |
| 5.94.0 | 5 / 5 | |
| 5.93.0 | 5 / 5 | |
| 5.92.0 | 5 / 5 | |
| 5.91.0 | 5 / 5 | |
| 5.90.0 | 5 / 5 | |
| 5.89.0 | 5 / 5 | |
| 5.88.0 | 5 / 5 | |
| 5.87.0 | 5 / 5 | |
| 5.86.0 | 5 / 5 | |
| 5.85.0 | 5 / 5 | |
| 5.84.1 | 5 / 5 | |
| 5.84.0 | 5 / 5 | |
| 5.83.0 | 5 / 5 | |
| 5.82.0 | 5 / 5 | |
| 5.81.0 | 5 / 5 |
v6.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.97.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.96.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.96.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.96.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.95.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.94.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.93.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.92.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.91.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.90.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.89.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.88.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.87.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.86.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.85.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.84.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.84.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.83.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-23. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.82.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.81.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-18. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.