computesdk
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): Transition to GitHub Actions CI/CD with SLSA attestation; benign for this package. | ai | |
| provenance | missing-githead | AI (provenance): Expected artifact of CI/CD publish transition, not a compromise indicator. | ai | |
| provenance | no-provenance | AI (provenance): Package consistently published without provenance; not a security signal for this package. | ai | |
| dependencies | unvetted-dep:@computesdk/cmd | AI (dependencies): First-party monorepo sibling package; workspace:* constraint confirms internal dep, not a third-party risk. | ai | |
| dependencies | unvetted-dep:@computesdk/client | AI (dependencies): First-party monorepo sibling package; workspace:* constraint confirms internal dep, not a third-party risk. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a declared runtime dep; phantom-dep fires because it's used indirectly via @computesdk/client, not directly imported. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a declared runtime dep; phantom-dep fires because it's used indirectly via @computesdk/client, not directly imported. | ai | |
| phantom-deps | phantom-dep:@computesdk/cmd | AI (phantom-deps): Sibling scoped dep used in config files, not direct imports; stable false positive for this package. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 4.1.4 | 2 / 7 | |
| 4.1.3 | 2 / 7 | |
| 4.1.2 | 2 / 7 | |
| 4.1.1 | 2 / 7 | |
| 4.1.0 | 2 / 7 | |
| 4.0.0 | 1 / 7 | |
| 3.0.0 | 1 / 7 | |
| 2.6.0 | 1 / 7 | |
| 2.5.4 | 1 / 7 | |
| 2.5.3 | 1 / 7 | |
| 2.5.2 | 1 / 7 | |
| 2.5.1 | 1 / 7 | |
| 2.5.0 | 1 / 7 | |
| 2.4.0 | 1 / 7 | |
| 2.3.0 | 1 / 7 | |
| 2.2.1 | 1 / 7 | |
| 2.2.0 | 1 / 7 | |
| 2.1.2 | 1 / 7 | |
| 2.1.1 | 1 / 7 | |
| 2.0.2 | 1 / 7 | |
| 2.0.1 | 1 / 7 | |
| 1.21.1 | 1 / 7 | |
| 1.21.0 | 1 / 7 | |
| 1.20.0 | 1 / 7 | |
| 1.19.0 | 1 / 7 | |
| 1.18.2 | 1 / 7 | |
| 1.18.1 | 1 / 7 | |
| 1.18.0 | 1 / 7 | |
| 1.17.0 | 1 / 7 | |
| 1.16.0 | 1 / 7 | |
| 1.15.0 | 1 / 7 | |
| 1.13.0 | 1 / 7 | |
| 1.12.1 | 1 / 7 | |
| 1.12.0 | 1 / 7 | |
| 1.11.1 | 1 / 7 | |
| 1.11.0 | 1 / 7 | |
| 1.10.3 | 1 / 7 | |
| 1.10.2 | 1 / 7 | |
| 1.10.1 | 1 / 7 | |
| 1.10.0 | 2 / 7 | |
| 1.9.6 | 2 / 7 | |
| 1.9.5 | 2 / 7 | |
| 1.9.4 | 2 / 7 | |
| 1.9.3 | 2 / 7 | |
| 1.9.2 | 2 / 7 | |
| 1.9.1 | 2 / 7 | |
| 1.9.0 | 2 / 7 | |
| 1.8.8 | 1 / 7 | |
| 1.8.7 | 1 / 7 | |
| 1.8.6 | 1 / 7 | |
| 1.8.5 | 3 / 8 |
v4.1.4
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 (heygarrison) on 2026-07-20, 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.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heygarrison.
v2.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heygarrison.
v2.5.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heygarrison.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heygarrison.
v1.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heygarrison.
v1.13.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heygarrison.
v1.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heygarrison.
v1.10.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heygarrison.