@atcute/lex-cli
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): New files correspond to expanded lexicon/identity resolution features; consistent with package purpose. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps are @atcute/* first-party packages from the same monorepo; not third-party supply-chain risk. | ai | |
| dependencies | unvetted-dep:@atcute/lexicon-resolver | AI (dependencies): Same-org @atcute/* package; consistent with the package's ecosystem and publisher track record. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @atcute packages; not a risk signal for this publisher. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 10 / 3 | |
| 3.0.1 | 10 / 3 | |
| 3.0.0 | 10 / 3 | |
| 2.8.2 | 10 / 3 | |
| 2.8.1 | 10 / 3 | |
| 2.8.0 | 10 / 3 | |
| 2.7.0 | 10 / 3 | |
| 2.6.1 | 10 / 3 | |
| 2.6.0 | 10 / 2 | |
| 2.5.3 | 10 / 2 | |
| 2.5.2 | 10 / 2 | |
| 2.5.1 | 10 / 2 | |
| 2.5.0 | 10 / 2 | |
| 2.4.0 | 6 / 3 | |
| 2.3.3 | 6 / 3 |
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.