← Home

@computesdk/secure-exec

Secure execution provider for ComputeSDK - isolated sandbox environments using secure-exec

12
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

heygarrison

Keywords

computesdksecure-execsandboxcode-executionpythonjavascriptcomputeproviderisolatedvm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:computesdk AI (phantom-deps): computesdk is a declared runtime dependency; phantom-dep heuristic fires incorrectly here. ai

Versions (showing 12 of 12)

Version Deps Published
0.1.11 4 / 8
0.1.10 4 / 8
0.1.9 4 / 8
0.1.8 4 / 8
0.1.7 4 / 8
0.1.6 4 / 8
0.1.5 4 / 8
0.1.4 3 / 8
0.1.3 3 / 8
0.1.2 3 / 8
0.1.1 3 / 8
0.1.0 3 / 8

v0.1.11

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: heygarrison → GitHub Actions (on 2026-07-20, now via trusted publisher with provenance) provenance

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.

v0.1.10

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: heygarrison → GitHub Actions (on 2026-05-29, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (heygarrison) on 2026-05-29, 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.