@kosdev-code/kos-ui-cli
Command-line interface for KOS workspace management and code generation.
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:@kosdev-code/kos-codegen-core | AI (phantom-deps): Same-org dep likely used indirectly via CLI entry point; stable false positive for this package. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): env spread is used to pass the current environment to a local npx child process — standard CLI tool pattern, no exfiltration. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP 127.0.0.1 is a localhost default for a local dev API server — expected in a development CLI scaffolding tool. | ai | |
| dependencies | unvetted-dep:create-nx-workspace | AI (dependencies): create-nx-workspace is a well-known Nx scaffolding tool; its use is expected in a CLI that scaffolds Nx workspaces. Pinning to 18.0.3 is responsible practice. | ai | |
| phantom-deps | phantom-dep:plop | AI (phantom-deps): plop is a CLI scaffolding tool invoked via config; not directly imported but legitimately used by this CLI package. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): prettier is used via config in CLI context; phantom-dep finding is a stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package is a CLI tool; minimal README, empty index.js, and no keywords are consistent with a binary-first package where logic lives in src/lib/cli.mjs. Not a spam/bogus package. | ai | |
| phantom-deps | phantom-dep:rimraf | AI (phantom-deps): rimraf is used via config/scripts in CLI context; phantom-dep finding is a stable false positive for this package. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 3.0.2 | 9 / 0 | |
| 2.1.40 | 8 / 0 | |
| 2.1.39 | 8 / 0 | |
| 2.1.38 | 8 / 0 | |
| 2.1.37 | 8 / 0 | |
| 2.1.36 | 8 / 0 | |
| 2.1.35 | 8 / 0 | |
| 2.1.34 | 8 / 0 | |
| 2.1.33 | 8 / 0 | |
| 2.1.32 | 8 / 0 | |
| 2.1.31 | 8 / 0 | |
| 2.1.30 | 8 / 0 | |
| 2.1.29 | 8 / 0 | |
| 2.1.28 | 8 / 0 | |
| 2.1.27 | 8 / 0 | |
| 2.1.26 | 8 / 0 | |
| 2.1.25 | 7 / 0 | |
| 2.1.23 | 7 / 0 | |
| 2.1.22 | 7 / 0 | |
| 2.1.21 | 7 / 0 | |
| 2.1.20 | 7 / 0 | |
| 2.1.19 | 7 / 0 | |
| 2.1.18 | 7 / 0 | |
| 2.1.17 | 7 / 0 | |
| 2.1.16 | 7 / 0 | |
| 2.1.15 | 7 / 0 | |
| 2.1.14 | 7 / 0 | |
| 2.1.13 | 7 / 0 | |
| 2.1.12 | 7 / 0 | |
| 2.1.11 | 7 / 0 | |
| 2.1.10 | 7 / 0 | |
| 2.1.9 | 7 / 0 | |
| 2.1.8 | 7 / 0 | |
| 2.1.7 | 7 / 0 | |
| 2.1.6 | 7 / 0 | |
| 2.1.5 | 7 / 0 | |
| 2.1.4 | 7 / 0 | |
| 2.1.3 | 7 / 0 | |
| 2.1.2 | 7 / 0 | |
| 2.1.1 | 7 / 0 | |
| 2.1.0 | 6 / 0 | |
| 2.0.46 | 6 / 0 | |
| 2.0.45 | 8 / 0 | |
| 2.0.44 | 6 / 0 | |
| 2.0.43 | 6 / 0 | |
| 2.0.42 | 6 / 0 | |
| 2.0.24 | 6 / 0 | |
| 2.0.8 | 6 / 0 | |
| 2.0.7 | 6 / 0 | |
| 2.0.5 | 6 / 0 |
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.45
2 findingsSpreading entire process.env into an object — may capture all secrets 102 | 103 | const proc = spawn("npx", ["nx", "run", `${project}:serve`], { > 104 | env: { 105 | ...process.env, 106 | ...env,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.