@oh-my-pi/pi-agent-core
General-purpose agent with transport abstraction, state management, and attachment support
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 | no-provenance | AI (provenance): New package without provenance setup; no other risk signals present. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 14.5.6 | 3 / 2 | |
| 13.16.5 | 2 / 2 | |
| 2.0.1337 | 2 / 2 | |
| 1.341.0 | 2 / 2 | |
| 1.337.1 | 2 / 2 | |
| 1.337.0 | 2 / 2 |
v14.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1337
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.341.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.337.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.337.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.