@cloudcommerce/app-pagarme
e-com.plus Cloud Commerce app to integrate Pagar.me
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:pagarme | AI (dependencies): pagarme is a known Brazilian payment SDK pinned to a specific version; stable dependency for this integration package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established monorepo package with 452 versions and clean diff; dormancy reflects release cadence, not takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo package; sparse README and no keywords are expected for internal integration packages. | ai | |
| phantom-deps | phantom-dep:firebase-admin | AI (phantom-deps): firebase-admin is a declared dependency used via config/runtime; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 2.59.5 | 7 / 2 | |
| 2.59.3 | 7 / 2 | |
| 2.59.0 | 7 / 2 | |
| 2.56.3 | 7 / 2 | |
| 2.56.0 | 7 / 2 | |
| 2.55.2 | 7 / 2 | |
| 2.55.1 | 7 / 2 | |
| 2.53.2 | 7 / 2 | |
| 2.53.0 | 7 / 2 | |
| 2.52.2 | 7 / 2 | |
| 2.52.1 | 7 / 2 | |
| 2.51.3 | 7 / 2 | |
| 2.51.1 | 7 / 2 | |
| 2.51.0 | 7 / 2 | |
| 2.50.1 | 7 / 2 | |
| 2.49.2 | 7 / 2 | |
| 2.49.0 | 7 / 2 | |
| 2.48.20 | 7 / 2 | |
| 2.48.15 | 7 / 2 | |
| 2.48.8 | 7 / 2 | |
| 2.48.5 | 7 / 2 | |
| 2.48.1 | 7 / 2 | |
| 2.46.0 | 7 / 2 | |
| 2.45.0 | 7 / 2 | |
| 2.44.8 | 7 / 2 | |
| 2.44.6 | 7 / 2 | |
| 2.44.3 | 7 / 2 | |
| 2.44.1 | 7 / 2 | |
| 2.42.4 | 7 / 2 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
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.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.52.2
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.51.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.51.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.49.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.15
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.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.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.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. Consider requesting the maintainer enable provenance via CI/CD.
v2.44.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.44.3
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.42.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.