@peac/mappings-a2a
Agent-to-Agent Protocol (A2A) 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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Package migrated to GitHub Actions CI/CD publishing with SLSA attestation; stable pattern for this package going forward. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.15.0 | 2 / 4 | |
| 0.14.5 | 2 / 4 | |
| 0.14.4 | 2 / 4 | |
| 0.14.3 | 2 / 4 | |
| 0.14.2 | 2 / 4 | |
| 0.14.1 | 2 / 4 | |
| 0.14.0 | 2 / 4 | |
| 0.13.4 | 2 / 4 | |
| 0.13.3 | 2 / 4 | |
| 0.13.2 | 2 / 4 | |
| 0.13.1 | 2 / 4 | |
| 0.13.0 | 2 / 4 | |
| 0.12.14 | 2 / 4 | |
| 0.12.13 | 2 / 4 | |
| 0.12.12 | 2 / 4 | |
| 0.12.11 | 2 / 4 | |
| 0.12.10 | 2 / 4 | |
| 0.12.9 | 2 / 4 | |
| 0.12.8 | 2 / 4 | |
| 0.12.7 | 2 / 4 | |
| 0.12.6 | 2 / 4 | |
| 0.12.5 | 2 / 4 | |
| 0.12.4 | 2 / 4 | |
| 0.12.3 | 2 / 4 | |
| 0.12.2 | 2 / 4 | |
| 0.12.1 | 2 / 4 | |
| 0.12.0 | 2 / 4 | |
| 0.11.3 | 2 / 4 | |
| 0.11.2 | 2 / 4 | |
| 0.11.1 | 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
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.3
2 findingsPublished 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-02. This could indicate a legitimate maintainer transition or an account compromise.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.