@unchainedshop/core-payment
Payment provider management module for the Unchained Engine
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| license | copyleft-license:EUPL-1.2 | AI (license): Declared EUPL-1.2 in package.json; stable for this package. | ai | |
| dependencies | unvetted-dep:expiry-map | AI (dependencies): expiry-map is a well-known, benign utility; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@unchainedshop/utils | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@unchainedshop/logger | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for monorepo packages. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 4.8.13 | 5 / 2 | |
| 4.8.12 | 5 / 2 | |
| 4.8.11 | 5 / 2 | |
| 4.8.9 | 5 / 2 | |
| 4.8.4 | 5 / 2 | |
| 4.8.3 | 5 / 2 | |
| 4.8.2 | 5 / 2 | |
| 4.7.2 | 5 / 2 | |
| 4.6.2 | 5 / 2 | |
| 4.6.0 | 5 / 2 | |
| 4.4.0 | 5 / 2 | |
| 4.3.3 | 5 / 3 | |
| 4.3.2 | 5 / 3 | |
| 4.3.1 | 5 / 3 | |
| 4.3.0 | 5 / 3 | |
| 4.1.3 | 5 / 3 | |
| 4.1.2 | 5 / 3 | |
| 4.1.1 | 5 / 3 | |
| 4.1.0 | 5 / 3 | |
| 4.0.2 | 5 / 3 | |
| 4.0.1 | 5 / 3 | |
| 4.0.0 | 5 / 3 |
v4.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.