@types/ci-info
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): This is a legitimate @types stub/redirect package from the DefinitelyTyped publisher. Minimal payload, no README code, and no repo URL are expected and stable for this package type. | ai | |
| phantom-deps | phantom-dep:ci-info | AI (phantom-deps): The ci-info dependency is intentional — it's the mechanism for redirecting users to the upstream package's bundled types. Not a phantom dep. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.1.4 | 1 / 0 | |
| 3.1.3 | 1 / 0 | |
| 3.1.2 | 1 / 0 | |
| 3.1.1 | 1 / 0 | |
| 3.1.0 | 1 / 0 | |
| 2.0.0 | 0 / 0 |
v3.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.