@js-eyes/server-core
JS Eyes HTTP + WebSocket server core
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 CI/CD publish transition, coincides with provenance improvement. | ai | |
| dependencies | unvetted-dep:@js-eyes/policy | AI (dependencies): First-party sibling package in same monorepo/publisher, not an unrelated third party. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Sibling package swap within same org's monorepo, benign refactor. | ai | |
| dependencies | unvetted-dep:@js-eyes/protocol | AI (dependencies): Internal monorepo sibling package under the same @js-eyes scope and publisher; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): New package family; lack of provenance is common and not a standalone risk signal here. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.10.0 | 4 / 0 | |
| 2.9.0 | 4 / 0 | |
| 2.8.5 | 4 / 0 | |
| 2.8.4 | 4 / 0 | |
| 2.8.3 | 4 / 0 | |
| 2.8.2 | 4 / 0 | |
| 2.8.1 | 4 / 0 | |
| 2.7.0 | 4 / 0 | |
| 2.6.2 | 4 / 0 | |
| 2.6.1 | 4 / 0 | |
| 2.6.0 | 4 / 0 | |
| 2.5.0 | 4 / 0 | |
| 2.4.0 | 4 / 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.
v2.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.