isolated-function — Greenflagged

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

kikobeats

Keywords

isolatedjavascriptjssandboxv8

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Trusted long-standing publisher; single version missing gitHead is not indicative of supply chain compromise.	ai	2026/05/23
semgrep	semgrep:env-spread	AI (semgrep): Package installs deps in subprocesses; env-spread is intentional to pass env to child process, not exfiltration.	ai	2026/05/07
semgrep	semgrep:child-process-import	AI (semgrep): Core functionality of a sandbox runner requires child_process; stable pattern for this package.	ai	2026/05/07
phantom-deps	phantom-dep:ensure-error	AI (phantom-deps): ensure-error is a declared runtime dep; phantom-dep heuristic false positive for this package.	ai	2026/05/07

Versions (showing 33 of 33)

Version	Deps	Published
0.1.64	8 / 22	2026-05-22
0.1.63	8 / 22	2026-05-22
0.1.62	8 / 22	2026-05-20
0.1.61	8 / 22	2026-05-20
0.1.60	8 / 22	2026-05-20
0.1.59	8 / 22	2026-05-20
0.1.58	8 / 22	2026-05-20
0.1.56	8 / 22	2026-05-19
0.1.55	8 / 13	2026-05-19
0.1.54	8 / 13	2026-05-18
0.1.53	8 / 13	2026-05-18
0.1.52	8 / 13	2026-04-14
0.1.51	8 / 14	2026-04-03
0.1.50	8 / 14	2026-03-18
0.1.49	8 / 14	2026-02-22
0.1.48	8 / 14	2025-12-02
0.1.47	8 / 14	2025-12-02
0.1.46	8 / 14	2025-12-02
0.1.45	8 / 14	2025-12-02
0.1.44	8 / 14	2025-12-02
0.1.43	8 / 14	2025-11-22
0.1.42	8 / 14	2025-11-10
0.1.41	8 / 14	2025-11-10
0.1.40	8 / 14	2025-10-21
0.1.39	8 / 14	2025-10-21
0.1.38	8 / 14	2025-10-21
0.1.37	8 / 14	2025-10-21
0.1.36	8 / 13	2025-10-20
0.1.35	8 / 13	2025-10-20
0.1.34	8 / 13	2025-10-14
0.1.33	8 / 13	2025-09-05
0.1.32	8 / 13	2025-06-09
0.1.31	8 / 13	2025-05-20

v0.1.64

1 finding

LOW No provenance attestation provenance

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

v0.1.63

1 finding

LOW No provenance attestation provenance

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

v0.1.62

1 finding

LOW No provenance attestation provenance

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

v0.1.61

1 finding

LOW No provenance attestation provenance

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

v0.1.60

1 finding

LOW No provenance attestation provenance

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

v0.1.59

1 finding

LOW No provenance attestation provenance

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

v0.1.58

1 finding

LOW No provenance attestation provenance

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

v0.1.56

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kikobeats.

LOW No provenance attestation provenance

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

v0.1.55

1 finding

LOW No provenance attestation provenance

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

v0.1.54

1 finding

LOW No provenance attestation provenance

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

v0.1.53

1 finding

LOW No provenance attestation provenance

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

v0.1.52

3 findings

HIGH env-spread: src/compile/install-dependencies.js:57 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/Kikobeats/isolated-function/blob/83c46fb5c0c8f06b64bd9b666e46296531c4dc53/src/compile/install-dependencies.js#L57 55 | module.exports = async ({ dependencies, cwd, allow = {} }) => { 56 | validateDependencies(dependencies, allow.dependencies) > 57 | return $(`${install} ${dependencies.join(' ')}`, { cwd, env: { ...process.env, CI: true } }) 58 | }

HIGH env-spread: src/index.js:41 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/Kikobeats/isolated-function/blob/83c46fb5c0c8f06b64bd9b666e46296531c4dc53/src/index.js#L41 39 | duration = timeSpan() 40 | const subprocess = $('node', ['-', JSON.stringify(args)], { > 41 | env: { 42 | ...process.env, 43 | NODE_OPTIONS: flags({ memory, permissions })

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.1.51

1 finding

LOW No provenance attestation provenance

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

v0.1.50

1 finding

LOW No provenance attestation provenance

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

v0.1.49

1 finding

LOW No provenance attestation provenance

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

v0.1.48

1 finding

LOW No provenance attestation provenance

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

v0.1.47

1 finding

LOW No provenance attestation provenance

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

v0.1.46

1 finding

LOW No provenance attestation provenance

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

v0.1.45

1 finding

LOW No provenance attestation provenance

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

v0.1.44

1 finding

LOW No provenance attestation provenance

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

v0.1.43

1 finding

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.1.42

1 finding

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.1.41

1 finding

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.1.40

1 finding

LOW No provenance attestation provenance

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

v0.1.39

1 finding

LOW No provenance attestation provenance

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

v0.1.38

1 finding

LOW No provenance attestation provenance

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

v0.1.37

1 finding

LOW No provenance attestation provenance

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

v0.1.36

1 finding

LOW No provenance attestation provenance

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

v0.1.35

1 finding

LOW No provenance attestation provenance

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

v0.1.34

1 finding

LOW No provenance attestation provenance

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

v0.1.33

1 finding

LOW No provenance attestation provenance

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

v0.1.32

1 finding

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.1.31

1 finding

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.