@amitte-ai/cli
Publisher CLI for the Amitte skills registry.
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @amitte-ai/cli is not a plausible typosquat of 'joi'; different scope, purpose, and structure. Levenshtein distance is coincidental. | ai | |
| phantom-deps | phantom-dep:@amitte-ai/sdk | AI (phantom-deps): Workspace sibling dependency in a monorepo; resolved at build time, not a phantom dep in the traditional sense. | ai | |
| phantom-deps | phantom-dep:@amitte-ai/shared | AI (phantom-deps): Workspace sibling dependency in a monorepo; resolved at build time, not a phantom dep in the traditional sense. | ai | |
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): yaml is a legitimate runtime dependency for a CLI tool that processes config files; low-signal finding. | ai | |
| phantom-deps | phantom-dep:undici | AI (phantom-deps): undici is a known implicit HTTP dependency; its use as a runtime/binary implicit dep is expected for this CLI package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.1.4 | 9 / 3 | |
| 0.1.3 | 9 / 3 | |
| 0.1.2 | 9 / 3 | |
| 0.1.1 | 9 / 3 | |
| 0.1.0 | 9 / 3 | |
| 0.0.1 | 9 / 3 |
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.