@kumori/kdsl
Kumori DSL command line interface and library
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 |
|---|---|---|---|---|
| license | uncommon-license:EUPL | AI (license): EUPL is a well-known EU open-source license; stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): Kumori org packages consistently lack provenance; not a malware signal for this package. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): chalk is a declared runtime dependency; phantom-dep heuristic fires incorrectly for this package. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): commander is a declared runtime dependency; phantom-dep heuristic fires incorrectly for this package. | ai | |
| phantom-deps | phantom-dep:@inquirer/prompts | AI (phantom-deps): @inquirer/prompts is a declared runtime dependency; phantom-dep heuristic fires incorrectly for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.0.54 | 7 / 6 | |
| 0.0.53 | 7 / 6 | |
| 0.0.52 | 7 / 6 | |
| 0.0.51 | 7 / 6 | |
| 0.0.50 | 7 / 6 | |
| 0.0.49 | 7 / 6 | |
| 0.0.44 | 7 / 6 | |
| 0.0.30 | 7 / 6 | |
| 0.0.16 | 7 / 6 |
v0.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.