@js-eyes/client-sdk
JS Eyes BrowserAutomation client SDK
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): Expected artifact of new CI/CD publish flow, not a compromise indicator. | ai | |
| dependencies | unvetted-dep:@js-eyes/policy | AI (dependencies): First-party sibling package under same org/monorepo, versioned in lockstep. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Internal sibling dependency added alongside matching version bump, not a foreign package. | ai | |
| dependencies | unvetted-dep:@js-eyes/protocol | AI (dependencies): Same-org scoped dep; part of the @js-eyes package family, consistent across versions. | ai | |
| provenance | no-provenance | AI (provenance): Common for small/new packages; no other risk signals present. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.10.0 | 4 / 0 | |
| 2.9.0 | 3 / 0 | |
| 2.8.5 | 3 / 0 | |
| 2.8.4 | 3 / 0 | |
| 2.8.3 | 3 / 0 | |
| 2.8.2 | 3 / 0 | |
| 2.8.1 | 3 / 0 | |
| 2.7.0 | 3 / 0 | |
| 2.6.2 | 3 / 0 | |
| 2.6.1 | 3 / 0 | |
| 2.6.0 | 3 / 0 | |
| 2.5.0 | 3 / 0 | |
| 2.4.0 | 3 / 0 |
v2.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 finding[Accepted risk] Package 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 2026-07-22, 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.