@types/ltx
2
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): @types/* packages on DefinitelyTyped are routinely dormant for years between library API changes; long dormancy is normal for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @types/events is a well-known DefinitelyTyped package; swapping @types/node for @types/events is a legitimate, minimal dependency refactor for a types-only package. | ai | |
| phantom-deps | phantom-dep:@types/events | AI (phantom-deps): Types-only packages use type dependencies structurally, not via direct import statements; phantom-dep false positive for @types/* packages. | ai |
v3.1.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.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.