@opena2a/check-core
Data-shape and orchestration primitives for the `check` command across OpenA2A CLIs. One implementation of input classification, registry → scan-on-miss flow, download-error translation, and canonical CheckOutput schema — consumed by hackmyagent, opena2a-
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@opena2a/registry-client | AI (phantom-deps): Same-org dep likely re-exported from dist; stable false positive for this package. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Package explicitly declares itself a 0.0.0 bootstrap placeholder; version is intentional namespace reservation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Intentional placeholder with empty payload; not spam or malicious. | ai |
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.