@cloudcommerce/api
e-com.plus Cloud Commerce APIs client/adapter
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:hapi | AI (typosquat): Scoped monorepo package; Levenshtein match to 'hapi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped monorepo package; Levenshtein match to 'pg' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped monorepo package; Levenshtein match to 'joi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped monorepo package; Levenshtein match to 'ajv' is a false positive. | ai |
Versions (showing 51 of 87)
| Version | Deps | Published |
|---|---|---|
| 2.60.3 | 0 / 0 | |
| 2.59.5 | 0 / 0 | |
| 2.59.4 | 0 / 0 | |
| 2.59.3 | 0 / 0 | |
| 2.59.2 | 0 / 0 | |
| 2.59.1 | 0 / 0 | |
| 2.59.0 | 0 / 0 | |
| 2.58.1 | 0 / 0 | |
| 2.58.0 | 0 / 0 | |
| 2.57.0 | 0 / 0 | |
| 2.56.4 | 0 / 0 | |
| 2.56.3 | 0 / 0 | |
| 2.56.2 | 0 / 0 | |
| 2.56.1 | 0 / 0 | |
| 2.56.0 | 0 / 0 | |
| 2.55.3 | 0 / 0 | |
| 2.55.2 | 0 / 0 | |
| 2.55.1 | 0 / 0 | |
| 2.55.0 | 0 / 0 | |
| 2.54.0 | 0 / 0 | |
| 2.53.2 | 0 / 0 | |
| 2.53.0 | 0 / 0 | |
| 2.52.2 | 0 / 0 | |
| 2.52.1 | 0 / 0 | |
| 2.52.0 | 0 / 0 | |
| 2.51.4 | 0 / 0 | |
| 2.51.3 | 0 / 0 | |
| 2.51.2 | 0 / 0 | |
| 2.51.1 | 0 / 0 | |
| 2.51.0 | 0 / 0 | |
| 2.50.1 | 0 / 0 | |
| 2.50.0 | 0 / 0 | |
| 2.49.5 | 0 / 0 | |
| 2.49.4 | 0 / 0 | |
| 2.49.3 | 0 / 0 | |
| 2.49.2 | 0 / 0 | |
| 2.49.1 | 0 / 0 | |
| 2.49.0 | 0 / 0 | |
| 2.48.20 | 0 / 0 | |
| 2.48.19 | 0 / 0 | |
| 2.48.18 | 0 / 0 | |
| 2.48.17 | 0 / 0 | |
| 2.48.16 | 0 / 0 | |
| 2.48.15 | 0 / 0 | |
| 2.48.14 | 0 / 0 | |
| 2.48.13 | 0 / 0 | |
| 2.48.12 | 0 / 0 | |
| 2.48.11 | 0 / 0 | |
| 2.48.10 | 0 / 0 | |
| 2.48.9 | 0 / 0 | |
| 2.48.8 | 0 / 0 |
v2.60.3
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.59.5
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.59.4
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.59.3
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.59.2
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.59.1
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.59.0
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.58.1
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.58.0
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.57.0
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.56.4
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.56.3
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.56.2
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.56.1
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.56.0
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.55.3
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.55.2
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.55.1
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.55.0
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.54.0
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.53.2
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.53.0
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.52.2
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.52.1
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.52.0
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.51.4
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.51.3
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.51.2
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.51.1
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.51.0
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.50.1
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.50.0
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.5
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.4
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.3
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.2
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.1
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.0
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.20
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.19
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.18
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.17
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.16
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.15
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.14
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.13
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.12
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.11
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.10
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.9
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.8
2 findingsPackage name '@cloudcommerce/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.