@cloudcommerce/app-pagaleve
e-com.plus Cloud Commerce app to integrate Pagaleve
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 596 approved packages and strong track record; dormancy likely reflects monorepo release cadence, not takeover. | ai | |
| dependencies | unvetted-dep:@cloudcommerce/api | AI (dependencies): Sibling package from the same cloudcommerce monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@cloudcommerce/firebase | AI (dependencies): Sibling package from the same cloudcommerce monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@ecomplus/utils | AI (dependencies): Known ecomplus ecosystem utility; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo app package; sparse README and no keywords are expected for internal integration packages. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo with 273 versions; lack of provenance is consistent across all versions. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 2.60.3 | 6 / 1 | |
| 2.59.5 | 6 / 1 | |
| 2.59.3 | 6 / 1 | |
| 2.58.1 | 6 / 1 | |
| 2.57.0 | 6 / 1 | |
| 2.56.3 | 6 / 1 | |
| 2.56.0 | 6 / 1 | |
| 2.55.2 | 6 / 1 | |
| 2.55.1 | 6 / 1 | |
| 2.53.2 | 6 / 1 | |
| 2.51.4 | 6 / 1 | |
| 2.51.3 | 6 / 1 | |
| 2.51.2 | 6 / 1 | |
| 2.51.0 | 6 / 1 | |
| 2.50.0 | 6 / 1 | |
| 2.48.20 | 6 / 1 | |
| 2.48.19 | 6 / 1 | |
| 2.48.13 | 6 / 1 | |
| 2.48.12 | 6 / 1 | |
| 2.48.8 | 6 / 1 | |
| 2.48.4 | 6 / 1 | |
| 2.48.2 | 6 / 1 | |
| 2.48.0 | 6 / 1 | |
| 2.46.3 | 6 / 1 | |
| 2.46.2 | 6 / 1 | |
| 2.46.1 | 6 / 1 | |
| 2.46.0 | 6 / 1 | |
| 2.45.5 | 6 / 1 | |
| 2.45.4 | 6 / 1 | |
| 2.44.8 | 6 / 1 | |
| 2.44.4 | 6 / 1 | |
| 2.43.1 | 6 / 1 | |
| 2.42.4 | 6 / 1 | |
| 2.42.3 | 6 / 1 | |
| 2.42.0 | 6 / 1 |
v2.60.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.58.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.56.3
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.51.4
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.2
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.0
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.13
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.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.2
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.46.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.46.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.45.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.45.4
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.4
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.3
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.