@peac/mappings-acp
Agentic Commerce Protocol (ACP) integration for PEAC
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@peac/kernel | AI (phantom-deps): Same org scope (@peac); sibling package dependency, stable false positive for this monorepo. | ai | |
| provenance | publisher-changed | AI (provenance): Package publishes via GitHub Actions CI with SLSA attestation; automated publisher is expected and consistent across versions. | ai | |
| phantom-deps | phantom-dep:@peac/protocol | AI (phantom-deps): Same-org monorepo dep declared in package.json; not directly imported at source level is expected for type/re-export packages. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.15.0 | 4 / 4 | |
| 0.14.5 | 4 / 4 | |
| 0.14.4 | 4 / 4 | |
| 0.14.3 | 4 / 4 | |
| 0.14.2 | 4 / 4 | |
| 0.14.1 | 4 / 4 | |
| 0.14.0 | 4 / 4 | |
| 0.13.4 | 4 / 4 | |
| 0.13.3 | 4 / 4 | |
| 0.13.2 | 4 / 4 | |
| 0.13.1 | 4 / 4 | |
| 0.13.0 | 4 / 4 | |
| 0.12.14 | 4 / 4 | |
| 0.12.13 | 4 / 4 | |
| 0.12.12 | 4 / 4 | |
| 0.12.11 | 4 / 4 | |
| 0.12.10 | 3 / 4 | |
| 0.12.9 | 3 / 4 | |
| 0.12.8 | 3 / 4 | |
| 0.12.7 | 3 / 4 | |
| 0.12.6 | 3 / 4 | |
| 0.12.5 | 3 / 4 | |
| 0.10.0 | 3 / 4 | |
| 0.9.31 | 3 / 4 | |
| 0.9.18 | 2 / 4 |
v0.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.5
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-03-28. This could indicate a legitimate maintainer transition or an account compromise.
v0.10.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: peacprotocol.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.