@a11d/lit
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Scoped package @a11d/lit is a Lit wrapper, not a typosquat of vite; edit-distance match is coincidental. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped package @a11d/lit is a Lit wrapper, not a typosquat of got; edit-distance match is coincidental. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.11.1 | 4 / 1 | |
| 0.11.0 | 4 / 1 | |
| 0.10.5 | 4 / 1 | |
| 0.10.4 | 4 / 1 | |
| 0.10.3 | 4 / 1 | |
| 0.10.2 | 4 / 1 | |
| 0.10.1 | 4 / 1 |
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.