@types/lz-string
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
types
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. Tiny payload, no README code, no repo URL, and no keywords are all expected for a deprecation stub pointing users to bundled types in lz-string. | ai | |
| phantom-deps | phantom-dep:lz-string | AI (phantom-deps): lz-string is listed as a dependency to pull in the real package per the @types stub pattern; it is not imported because this package contains no code by design. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.5.0 | 1 / 0 |
v1.5.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.