@athree/cli — Greenflagged

A3 CLI

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

mihonchristellevsincamarcusgreenwood_ubio

Keywords

athreea3

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:env-spread	AI (semgrep): CLI tool forwarding process.env to child process is standard; not a secret-exfiltration risk.	ai	2026/05/16
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped package @athree/cli bears no functional or naming resemblance to joi; Levenshtein match is spurious.	ai	2026/05/16

Versions (showing 37 of 37)

Version	Deps	Published
4.2.6	1 / 0	2026-05-22
4.2.5	1 / 0	2026-05-21
4.2.4	1 / 0	2026-05-21
4.2.3	1 / 0	2026-05-21
4.2.2	1 / 0	2026-05-21
4.2.1	1 / 0	2026-05-21
4.2.0	1 / 0	2026-05-21
4.1.2	1 / 0	2026-05-19
4.1.1	1 / 0	2026-04-30
4.1.0	1 / 0	2026-04-30
4.0.1	1 / 0	2026-04-23
4.0.0	1 / 0	2026-04-23
3.4.18	1 / 0	2026-04-15
3.4.17	1 / 0	2026-04-15
3.4.16	1 / 0	2026-04-15
3.4.15	1 / 0	2026-04-15
3.4.14	1 / 0	2026-04-15
3.4.13	1 / 0	2026-04-15
3.4.12	1 / 0	2026-04-07
3.4.11	1 / 0	2026-04-02
3.4.10	1 / 0	2026-04-01
3.4.9	1 / 0	2026-03-24
3.4.8	1 / 0	2026-03-24
3.4.7	1 / 0	2026-03-24
3.4.6	1 / 0	2026-03-23
3.4.5	1 / 0	2026-03-23
3.4.4	1 / 0	2026-03-20
3.4.3	1 / 0	2026-02-19
3.4.2	1 / 0	2026-02-16
3.4.1	1 / 0	2026-02-13
3.4.0	1 / 0	2026-02-13
3.3.0	1 / 0	2026-02-05
3.2.4	1 / 0	2026-02-02
3.2.3	1 / 0	2026-02-02
3.2.2	1 / 0	2026-01-29
3.2.1	1 / 0	2026-01-29
3.2.0	1 / 0	2026-01-29

v4.2.6

1 finding

LOW No provenance attestation provenance

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

v4.2.5

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: inca → mihon (on 2026-05-21, known maintainer) provenance

This version was published by a different npm account (mihon) than the most recent previously approved version (inca) on 2026-05-21, but mihon is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.2.4

1 finding

LOW No provenance attestation provenance

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

v4.2.3

1 finding

LOW No provenance attestation provenance

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

v4.2.2

1 finding

LOW No provenance attestation provenance

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

v4.2.1

1 finding

LOW No provenance attestation provenance

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

v4.2.0

1 finding

LOW No provenance attestation provenance

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

v4.1.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: inca → mihon (on 2026-05-19, known maintainer) provenance

This version was published by a different npm account (mihon) than the most recent previously approved version (inca) on 2026-05-19, but mihon is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.1.1

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:17 semgrep

Spreading entire process.env into an object — may capture all secrets 15 | stdio: 'inherit', 16 | cwd: projectDir, > 17 | env: { 18 | ...process.env, 19 | WORKFLOW_ID: workflowId,

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.

v4.1.0

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:17 semgrep

Spreading entire process.env into an object — may capture all secrets 15 | stdio: 'inherit', 16 | cwd: projectDir, > 17 | env: { 18 | ...process.env, 19 | WORKFLOW_ID: workflowId,

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.

v4.0.1

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:17 semgrep

Spreading entire process.env into an object — may capture all secrets 15 | stdio: 'inherit', 16 | cwd: projectDir, > 17 | env: { 18 | ...process.env, 19 | WORKFLOW_ID: workflowId,

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.

v4.0.0

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:17 semgrep

Spreading entire process.env into an object — may capture all secrets 15 | stdio: 'inherit', 16 | cwd: projectDir, > 17 | env: { 18 | ...process.env, 19 | WORKFLOW_ID: workflowId,

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.

v3.4.18

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.4.17

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.4.16

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.4.15

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.4.14

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.4.13

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.4.12

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.4.11

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.4.10

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.4.9

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.4.8

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.4.7

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.4.6

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.4.5

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.4.4

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.4.3

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.4.2

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.4.1

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.4.0

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.3.0

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.2.4

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.2.3

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.2.2

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.2.1

2 findings

HIGH env-spread: out/main/commands/RunWorkflow.js:20 semgrep

Spreading entire process.env into an object — may capture all secrets 18 | stdio: 'inherit', 19 | cwd: projectDir, > 20 | env: { 21 | ...process.env, 22 | WORKFLOW_ID: workflowId,

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.

v3.2.0

2 findings

HIGH env-spread: out/main/services/WorkflowRunner.js:16 semgrep

Spreading entire process.env into an object — may capture all secrets 14 | stdio: 'inherit', 15 | cwd: params.projectDir, > 16 | env: { 17 | ...process.env, 18 | WORKFLOW_ID: params.workflowId,

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.