@peac/adapter-openclaw
OpenClaw adapter for PEAC interaction evidence capture
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): Transition to GitHub Actions CI/CD publisher is confirmed by SLSA provenance attestation; legitimate automation change. | ai | |
| phantom-deps | phantom-dep:@peac/kernel | AI (phantom-deps): Same-org monorepo package; phantom-dep heuristic fires on re-exported transitive deps, stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@peac/schema | AI (phantom-deps): Same-org monorepo package; phantom-dep heuristic fires on re-exported transitive deps, stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@peac/adapter-core | AI (phantom-deps): Same-org monorepo package; phantom-dep heuristic fires on re-exported transitive deps, stable FP for this package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.15.0 | 6 / 4 | |
| 0.14.5 | 6 / 4 | |
| 0.14.4 | 6 / 4 | |
| 0.14.3 | 6 / 4 | |
| 0.14.2 | 6 / 4 | |
| 0.14.1 | 6 / 4 | |
| 0.14.0 | 6 / 4 | |
| 0.13.4 | 6 / 4 | |
| 0.13.3 | 6 / 4 | |
| 0.13.2 | 6 / 4 | |
| 0.13.1 | 6 / 4 | |
| 0.13.0 | 6 / 4 | |
| 0.12.14 | 6 / 4 | |
| 0.12.13 | 6 / 4 | |
| 0.12.12 | 6 / 4 | |
| 0.12.11 | 6 / 4 | |
| 0.12.10 | 6 / 4 | |
| 0.12.9 | 6 / 4 | |
| 0.12.8 | 6 / 4 | |
| 0.12.7 | 6 / 4 | |
| 0.12.6 | 6 / 4 | |
| 0.10.13 | 6 / 4 | |
| 0.10.9 | 5 / 3 | |
| 0.10.7 | 5 / 3 |
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.10.13
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.10.9
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.
This version was published by a different npm account than previous versions on 2026-02-08. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.