@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 | publisher-changed | AI (provenance): Legitimate move to GitHub Actions CI/CD publishing with SLSA attestation. | ai | |
| dependencies | unvetted-dep:@oh-my-pi/pi-catalog | AI (dependencies): First-party monorepo sibling package pinned to same version. | ai | |
| provenance | missing-githead | AI (provenance): Expected side effect of manual->CI/CD publish migration, not compromise. | ai | |
| provenance | no-provenance | AI (provenance): New package without provenance setup; no other risk signals present. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 16.3.2 | 7 / 3 | |
| 16.2.8 | 7 / 3 | |
| 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 |
v16.3.2
3 findings[Reject — re-review on republish] (prior reject: AI (provenance): Prior versions had gitHead; its absence confirms publish environment changed unexpectedly.) This 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-07-02. 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.
v16.2.8
3 findings[Reject — re-review on republish] (prior reject: AI (provenance): Prior versions had gitHead; its absence confirms publish environment changed unexpectedly.) This 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-06-30. 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.