@js-eyes/protocol
Shared protocol constants for JS Eyes runtime packages
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): CI publish provenance-attested; minor metadata gap, not a compromise signal. | ai | |
| dependencies | unvetted-dep:@js-eyes/skill-contract | AI (dependencies): Same-org sibling package in the js-eyes monorepo, versioned in lockstep. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Internal monorepo dependency, not third-party supply chain risk. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): process.env spread is used to pass environment to a subprocess with a single override — standard subprocess launcher pattern. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Used in safe-npm.js with an explicit ALLOWED_SUBCOMMANDS allowlist; intentional sandboxed npm wrapper. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Plugin/skill loader pattern in skills.js; consistent with package's documented purpose. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.10.0 | 0 / 0 | |
| 2.9.0 | 1 / 0 | |
| 2.8.5 | 0 / 0 | |
| 2.8.4 | 0 / 0 | |
| 2.8.3 | 0 / 0 | |
| 2.8.2 | 0 / 0 | |
| 2.8.1 | 0 / 0 | |
| 2.7.0 | 0 / 0 | |
| 2.6.2 | 0 / 0 | |
| 2.6.1 | 0 / 0 | |
| 2.6.0 | 0 / 0 | |
| 2.5.0 | 0 / 0 | |
| 2.4.0 | 0 / 0 |
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.5
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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (imjszhang) on unknown date, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v2.8.4
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: imjszhang.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.