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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@darkroom.engineering/tempus | AI (dependencies): First-party sibling package from same org/monorepo, not third-party unvetted code. | ai | |
| phantom-deps | phantom-dep:@darkroom.engineering/tempus | AI (phantom-deps): Used via config/build tooling, standard heuristic false positive. | ai | |
| typosquat | typosquat.levenshtein:redis | AI (typosquat): lenis is its own established brand (643k downloads, 1144 days old); Levenshtein proximity to redis is coincidental. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 1.3.25 | 0 / 3 | |
| 1.3.24 | 0 / 3 | |
| 1.3.23 | 0 / 3 | |
| 1.3.22 | 0 / 3 | |
| 1.3.21 | 0 / 3 | |
| 1.3.20 | 0 / 3 | |
| 1.3.19 | 0 / 4 | |
| 1.3.18 | 0 / 4 | |
| 1.3.17 | 0 / 3 | |
| 1.3.16 | 0 / 3 | |
| 1.3.15 | 0 / 3 | |
| 1.3.14 | 0 / 3 | |
| 1.3.13 | 0 / 3 | |
| 1.3.12 | 0 / 3 | |
| 1.3.11 | 0 / 3 | |
| 1.3.10 | 0 / 3 | |
| 1.3.9 | 0 / 3 | |
| 1.3.8 | 0 / 3 | |
| 1.3.7 | 0 / 3 | |
| 1.3.6 | 0 / 3 | |
| 1.3.5 | 0 / 3 | |
| 1.3.4 | 0 / 3 | |
| 1.3.3 | 0 / 3 | |
| 1.3.2 | 0 / 3 | |
| 1.3.1 | 0 / 3 | |
| 1.3.0 | 0 / 3 | |
| 1.2.3 | 0 / 3 | |
| 1.2.2 | 0 / 3 | |
| 1.2.1 | 0 / 3 | |
| 1.2.0 | 0 / 3 | |
| 1.1.22 | 0 / 3 | |
| 1.1.21 | 0 / 3 | |
| 1.1.20 | 0 / 3 | |
| 1.1.19 | 0 / 3 | |
| 1.1.18 | 0 / 2 | |
| 1.1.17 | 0 / 2 | |
| 1.1.16 | 0 / 2 | |
| 1.1.15 | 0 / 2 | |
| 1.1.14 | 1 / 2 | |
| 1.1.13 | 1 / 14 | |
| 1.1.12 | 1 / 14 | |
| 1.1.11 | 1 / 14 | |
| 1.1.10 | 1 / 14 | |
| 1.1.9 | 1 / 14 | |
| 1.1.8 | 1 / 14 | |
| 1.1.7 | 1 / 14 | |
| 1.1.6 | 1 / 14 | |
| 1.1.5 | 1 / 14 | |
| 1.1.4 | 1 / 14 | |
| 1.1.3 | 1 / 14 | |
| 1.1.2 | 1 / 14 |
v1.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.