← Home

@blueagent/cli

npm

BlueAgent TUI — terminal UI for 31 x402 security and research tools

40
Versions
MIT
License
No
Install Scripts
Missing
Provenance

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

madebyshun

Keywords

blueagentclituix402basesecuritybuilderagent

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Spreading process.env into execP options is a standard pattern for subprocess env inheritance; no exfiltration or attacker-controlled destination involved. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped package @blueagent/cli is not plausibly confused with joi; completely different purpose and namespace. Levenshtein distance of 2 is a false positive here. ai

Versions (showing 40 of 40)

Version Deps Published
1.3.14 7 / 3
1.3.13 7 / 3
1.3.12 7 / 3
1.3.10 7 / 3
1.3.9 7 / 3
1.3.8 7 / 3
1.3.7 7 / 3
1.3.5 7 / 3
1.3.4 7 / 3
1.3.3 7 / 3
1.3.2 7 / 3
1.3.0 7 / 3
1.2.12 7 / 3
1.2.11 7 / 3
1.2.10 7 / 3
1.2.9 7 / 3
1.2.8 7 / 3
1.2.6 7 / 3
1.2.4 7 / 3
1.2.3 7 / 3
1.2.2 7 / 3
1.2.1 7 / 3
1.2.0 7 / 3
1.1.17 7 / 4
1.1.16 6 / 4
1.1.13 6 / 4
1.1.12 6 / 4
1.1.11 6 / 4
1.1.10 6 / 4
1.1.9 5 / 4
1.1.8 5 / 4
1.1.7 5 / 4
1.1.6 5 / 4
1.1.5 5 / 4
1.1.4 5 / 4
1.1.1 5 / 4
1.1.0 5 / 4
1.0.2 7 / 5
1.0.1 7 / 5
1.0.0 7 / 5

v1.3.14

1 finding
LOW No provenance attestation provenance

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

v1.3.13

1 finding
LOW No provenance attestation provenance

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

v1.3.12

1 finding
LOW No provenance attestation provenance

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

v1.3.10

1 finding
LOW No provenance attestation provenance

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

v1.3.9

1 finding
LOW No provenance attestation provenance

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

v1.3.8

1 finding
LOW No provenance attestation provenance

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

v1.3.7

1 finding
LOW No provenance attestation provenance

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

v1.3.5

1 finding
LOW No provenance attestation provenance

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

v1.3.4

1 finding
LOW No provenance attestation provenance

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

v1.3.3

1 finding
LOW No provenance attestation provenance

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

v1.3.2

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.12

1 finding
LOW No provenance attestation provenance

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

v1.2.11

1 finding
LOW No provenance attestation provenance

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

v1.2.10

1 finding
LOW No provenance attestation provenance

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

v1.2.9

1 finding
LOW No provenance attestation provenance

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

v1.2.8

1 finding
LOW No provenance attestation provenance

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

v1.2.6

1 finding
LOW No provenance attestation provenance

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

v1.2.4

1 finding
LOW No provenance attestation provenance

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

v1.2.3

1 finding
LOW No provenance attestation provenance

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

v1.2.2

1 finding
LOW No provenance attestation provenance

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

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.17

1 finding
LOW No provenance attestation provenance

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

v1.1.16

1 finding
LOW No provenance attestation provenance

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

v1.1.13

1 finding
LOW No provenance attestation provenance

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

v1.1.12

1 finding
LOW No provenance attestation provenance

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

v1.1.11

1 finding
LOW No provenance attestation provenance

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

v1.1.10

1 finding
LOW No provenance attestation provenance

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

v1.1.9

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.

v1.1.8

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.

v1.1.7

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.

v1.1.6

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.

v1.1.5

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.

v1.1.4

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.

v1.1.1

2 findings
HIGH env-spread: src/cli.ts:114 semgrep

Spreading entire process.env into an object — may capture all secrets 112 | const { stdout } = await execP(cmd, { 113 | timeout: 60000, > 114 | env: { ...process.env, BANKR_API_KEY: apiKey }, 115 | }) 116 |

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.

v1.1.0

2 findings
HIGH env-spread: src/cli.ts:105 semgrep

Spreading entire process.env into an object — may capture all secrets 103 | const { stdout } = await execP(cmd, { 104 | timeout: 60000, > 105 | env: { ...process.env, BANKR_API_KEY: apiKey }, 106 | }) 107 |

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.

v1.0.2

2 findings
HIGH env-spread: src/cli.ts:105 semgrep

Spreading entire process.env into an object — may capture all secrets 103 | const { stdout } = await execP(cmd, { 104 | timeout: 60000, > 105 | env: { ...process.env, BANKR_API_KEY: apiKey }, 106 | }) 107 |

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.

v1.0.1

2 findings
HIGH env-spread: src/cli.ts:105 semgrep

Spreading entire process.env into an object — may capture all secrets 103 | const { stdout } = await execP(cmd, { 104 | timeout: 60000, > 105 | env: { ...process.env, BANKR_API_KEY: apiKey }, 106 | }) 107 |

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.

v1.0.0

2 findings
HIGH env-spread: src/cli.ts:105 semgrep

Spreading entire process.env into an object — may capture all secrets 103 | const { stdout } = await execP(cmd, { 104 | timeout: 60000, > 105 | env: { ...process.env, BANKR_API_KEY: apiKey }, 106 | }) 107 |

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.