@tempfix/lenis
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:redis | AI (typosquat): Package is a scoped fork of lenis, not a typosquat of redis; levenshtein match is coincidental. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.3.20 | 0 / 3 | |
| 1.3.19 | 0 / 3 | |
| 1.3.18 | 0 / 3 | |
| 1.3.17 | 0 / 3 |
v1.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.