← Home

@effectstream/near-sandbox

npm Repository Homepage

NEAR sandbox binary wrapper for EffectStream

11
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

edwarddc

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Standard child-process env-forwarding pattern for a sandbox binary wrapper; not credential exfiltration. ai

Versions (showing 11 of 11)

Version Deps Published
0.100.18 1 / 0
0.100.17 1 / 0
0.100.16 1 / 0
0.100.15 1 / 0
0.100.14 1 / 0
0.100.13 1 / 0
0.100.12 1 / 0
0.100.11 1 / 0
0.100.10 1 / 0
0.100.9 1 / 0
0.100.8 1 / 0

v0.100.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.100.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.100.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.100.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.100.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.100.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.100.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.100.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.100.10

2 findings
HIGH env-spread: index.js:92 semgrep

Spreading entire process.env into an object — may capture all secrets 90 | ]; 91 | const child = execFile(bin.path(), args, { > 92 | env: { 93 | ...process.env, 94 | NEAR_SANDBOX_RPC_PORT: String(rpcPort),

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.100.9

2 findings
HIGH env-spread: index.js:92 semgrep

Spreading entire process.env into an object — may capture all secrets 90 | ]; 91 | const child = execFile(bin.path(), args, { > 92 | env: { 93 | ...process.env, 94 | NEAR_SANDBOX_RPC_PORT: String(rpcPort),

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.100.8

2 findings
HIGH env-spread: index.js:92 semgrep

Spreading entire process.env into an object — may capture all secrets 90 | ]; 91 | const child = execFile(bin.path(), args, { > 92 | env: { 93 | ...process.env, 94 | NEAR_SANDBOX_RPC_PORT: String(rpcPort),

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.