@cloudcommerce/cli
e-com.plus Cloud Commerce CLI tools
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 @cloudcommerce/cli package in a known monorepo; Levenshtein match to 'joi' is coincidental. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes GitHub Actions public key for libsodium encryption — standard GitHub Secrets API usage, not obfuscation. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): typescript is a declared runtime dep used as a build tool; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 2.59.5 | 10 / 0 | |
| 2.59.4 | 10 / 0 | |
| 2.59.3 | 10 / 0 | |
| 2.59.2 | 10 / 0 | |
| 2.58.0 | 10 / 0 | |
| 2.56.2 | 10 / 0 | |
| 2.56.1 | 10 / 0 | |
| 2.56.0 | 10 / 0 | |
| 2.55.2 | 10 / 0 | |
| 2.55.1 | 10 / 0 | |
| 2.53.0 | 10 / 0 | |
| 2.52.1 | 10 / 0 | |
| 2.52.0 | 10 / 0 | |
| 2.51.3 | 10 / 0 | |
| 2.51.0 | 10 / 0 | |
| 2.50.1 | 10 / 0 | |
| 2.49.5 | 10 / 0 | |
| 2.49.4 | 10 / 0 | |
| 2.49.3 | 10 / 0 | |
| 2.48.20 | 10 / 0 | |
| 2.48.19 | 10 / 0 | |
| 2.48.12 | 10 / 0 | |
| 2.48.9 | 10 / 0 | |
| 2.48.6 | 10 / 0 | |
| 2.48.3 | 10 / 0 | |
| 2.48.0 | 10 / 0 | |
| 2.46.3 | 10 / 0 | |
| 2.45.3 | 10 / 0 | |
| 2.45.2 | 10 / 0 | |
| 2.45.0 | 10 / 0 | |
| 2.44.8 | 10 / 0 | |
| 2.44.5 | 10 / 0 | |
| 2.44.4 | 10 / 0 | |
| 2.44.1 | 10 / 0 | |
| 2.43.1 | 9 / 0 | |
| 2.42.4 | 9 / 0 | |
| 2.42.1 | 9 / 0 | |
| 2.42.0 | 9 / 0 |
v2.59.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.59.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.59.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.59.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.56.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.56.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.55.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.55.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.52.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.51.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.50.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.46.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.45.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.45.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.44.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.44.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.44.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.44.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.43.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.