@types/wrap-ansi
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Stub @types packages rarely need updates; dormant-then-deprecate is a normal lifecycle for this publisher and package type. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Adding wrap-ansi as a dependency is the explicit purpose of this stub package — it redirects users to the upstream bundled types. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Stub @types deprecation packages are intentionally minimal with no code, no README instructions, and no keywords — this is expected for this package type. | ai | |
| phantom-deps | phantom-dep:wrap-ansi | AI (phantom-deps): Stub @types packages declare upstream as a dependency without importing it; this is the intended redirect mechanism, not a phantom dep. | ai |
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.