@kompojs/cli
Kompo CLI - Web3 Component as a Service
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is declared as a dependency; likely used in templates/config files of this CLI scaffolding tool. | ai | |
| phantom-deps | phantom-dep:openai | AI (phantom-deps): openai is declared as a dependency; likely used in generated/template code by this CLI tool. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): fs-extra is declared as a dependency; likely used in templates or config files of this CLI tool. | ai | |
| provenance | no-provenance | AI (provenance): New package in active development; lack of provenance attestation is a process concern, not a security signal for this package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @kompojs/cli is a scoped CLI package for the Kompo framework; edit-distance match to 'joi' is a false positive with no functional or naming similarity. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.1.7 | 16 / 6 | |
| 0.1.6 | 16 / 6 | |
| 0.1.5 | 16 / 6 | |
| 0.1.3 | 16 / 6 | |
| 0.1.2 | 16 / 6 | |
| 0.1.1 | 16 / 6 | |
| 0.1.0 | 16 / 6 |
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.