← Home

@aiready/cli

npm Repository Homepage
88
Versions
—
License
Yes
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

caopeng

Keywords

aireadycliAgentic ReadinessModel Context ProtocolMCPCursorWindsurfClaudeCopilotai-readinesscode-analysissemantic-duplicatescontext-windowagentic-developmentcode-qualitystatic-analysisdeveloper-toolsvscode-extension

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@aiready/deps AI (phantom-deps): Same-org scoped dep; likely consumed transitively within the @aiready monorepo. ai
phantom-deps phantom-dep:@aiready/doc-drift AI (phantom-deps): Same-org scoped dep; likely consumed transitively within the @aiready monorepo. ai
phantom-deps phantom-dep:@aiready/agent-grounding AI (phantom-deps): Same-org scoped dep; likely consumed transitively within the @aiready monorepo. ai
phantom-deps phantom-dep:@aiready/ai-signal-clarity AI (phantom-deps): Same-org scoped dep; likely consumed transitively within the @aiready monorepo. ai
semgrep semgrep:env-spread AI (semgrep): Spreading process.env into spawn options is standard CLI practice; not a secret-exfiltration risk here. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @aiready namespace; edit-distance match to 'joi' is coincidental, not impersonation. ai

Versions (showing 88 of 88)

Version Deps Published
0.15.37 14 / 2
0.15.27 14 / 2
0.15.26 14 / 2
0.15.24 14 / 2
0.15.21 14 / 2
0.15.16 14 / 2
0.15.11 14 / 2
0.15.9 14 / 2
0.15.2 14 / 2
0.14.25 13 / 2
0.14.24 13 / 2
0.14.17 13 / 2
0.9.43 13 / 2
0.9.40 13 / 2
0.9.35 7 / 2
0.9.33 7 / 2
0.9.30 7 / 2
0.9.29 7 / 2
0.9.28 7 / 2
0.9.27 7 / 2
0.9.26 7 / 2
0.9.25 7 / 2
0.9.24 7 / 2
0.9.23 7 / 2
0.9.21 7 / 2
0.9.20 7 / 2
0.9.19 7 / 2
0.9.18 7 / 2
0.9.17 7 / 2
0.9.15 7 / 2
0.9.14 7 / 2
0.9.13 7 / 2
0.9.12 7 / 2
0.9.11 7 / 2
0.9.10 7 / 2
0.9.9 7 / 2
0.9.7 7 / 2
0.9.6 7 / 2
0.9.5 7 / 2
0.9.2 6 / 2
0.9.1 6 / 2
0.9.0 6 / 2
0.8.1 6 / 2
0.8.0 6 / 2
0.7.21 6 / 2
0.7.20 6 / 2
0.7.19 6 / 2
0.7.18 6 / 2
0.7.17 6 / 2
0.7.16 6 / 2
0.7.15 6 / 2
0.7.14 6 / 2
0.7.13 6 / 2
0.7.11 6 / 2
0.7.10 6 / 2
0.7.9 6 / 2
0.7.8 6 / 2
0.7.7 6 / 2
0.7.6 6 / 2
0.7.5 6 / 2
0.7.4 6 / 2
0.7.3 6 / 2
0.7.2 6 / 2
0.7.1 6 / 2
0.7.0 6 / 2
0.6.0 6 / 2
0.5.1 6 / 2
0.5.0 6 / 2
0.4.5 6 / 2
0.4.4 6 / 2
0.4.3 6 / 2
0.4.2 6 / 2
0.4.1 6 / 2
0.4.0 6 / 2
0.3.8 5 / 2
0.3.7 5 / 2
0.3.6 5 / 2
0.3.5 5 / 2
0.3.4 5 / 2
0.3.3 5 / 2
0.3.2 5 / 2
0.3.1 5 / 2
0.2.1 5 / 2
0.2.0 5 / 2
0.1.4 5 / 2
0.1.3 5 / 2
0.1.2 5 / 2
0.1.0 5 / 2

v0.15.37

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

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

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

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

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

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

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

v0.15.2

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

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

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

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

2 findings
HIGH env-spread: src/commands/visualize.ts:173 semgrep

Spreading entire process.env into an object — may capture all secrets 171 | }); 172 | > 173 | const envForSpawn = { 174 | ...process.env, 175 | AIREADY_REPORT_PATH: reportPath,

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

2 findings
HIGH env-spread: src/commands/visualize.ts:146 semgrep

Spreading entire process.env into an object — may capture all secrets 144 | }); 145 | > 146 | const envForSpawn = { 147 | ...process.env, 148 | AIREADY_REPORT_PATH: reportPath,

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

2 findings
HIGH env-spread: src/commands/visualize.ts:146 semgrep

Spreading entire process.env into an object — may capture all secrets 144 | }); 145 | > 146 | const envForSpawn = { 147 | ...process.env, 148 | AIREADY_REPORT_PATH: reportPath,

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

2 findings
HIGH env-spread: src/commands/visualize.ts:146 semgrep

Spreading entire process.env into an object — may capture all secrets 144 | }); 145 | > 146 | const envForSpawn = { 147 | ...process.env, 148 | AIREADY_REPORT_PATH: reportPath,

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

2 findings
HIGH env-spread: src/commands/visualize.ts:146 semgrep

Spreading entire process.env into an object — may capture all secrets 144 | }); 145 | > 146 | const envForSpawn = { 147 | ...process.env, 148 | AIREADY_REPORT_PATH: reportPath,

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

2 findings
HIGH env-spread: src/commands/visualize.ts:146 semgrep

Spreading entire process.env into an object — may capture all secrets 144 | }); 145 | > 146 | const envForSpawn = { 147 | ...process.env, 148 | AIREADY_REPORT_PATH: reportPath,

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

2 findings
HIGH env-spread: src/commands/visualize.ts:144 semgrep

Spreading entire process.env into an object — may capture all secrets 142 | }); 143 | > 144 | const envForSpawn = { 145 | ...process.env, 146 | AIREADY_REPORT_PATH: reportPath,

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

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

Spreading entire process.env into an object — may capture all secrets 1268 | }); 1269 | > 1270 | const envForSpawn = { 1271 | ...process.env, 1272 | AIREADY_REPORT_PATH: reportPath,

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

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

Spreading entire process.env into an object — may capture all secrets 1314 | }); 1315 | > 1316 | const envForSpawn = { 1317 | ...process.env, 1318 | AIREADY_REPORT_PATH: reportPath,

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

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

Spreading entire process.env into an object — may capture all secrets 1314 | }); 1315 | > 1316 | const envForSpawn = { 1317 | ...process.env, 1318 | AIREADY_REPORT_PATH: reportPath,

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

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

Spreading entire process.env into an object — may capture all secrets 1314 | }); 1315 | > 1316 | const envForSpawn = { 1317 | ...process.env, 1318 | AIREADY_REPORT_PATH: reportPath,

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

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

Spreading entire process.env into an object — may capture all secrets 1314 | }); 1315 | > 1316 | const envForSpawn = { 1317 | ...process.env, 1318 | AIREADY_REPORT_PATH: reportPath,

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

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

Spreading entire process.env into an object — may capture all secrets 1314 | }); 1315 | > 1316 | const envForSpawn = { 1317 | ...process.env, 1318 | AIREADY_REPORT_PATH: reportPath,

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

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

Spreading entire process.env into an object — may capture all secrets 1314 | }); 1315 | > 1316 | const envForSpawn = { 1317 | ...process.env, 1318 | AIREADY_REPORT_PATH: reportPath,

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

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

Spreading entire process.env into an object — may capture all secrets 1314 | }); 1315 | > 1316 | const envForSpawn = { 1317 | ...process.env, 1318 | AIREADY_REPORT_PATH: reportPath,

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

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

Spreading entire process.env into an object — may capture all secrets 1234 | }); 1235 | > 1236 | const envForSpawn = { ...process.env, AIREADY_REPORT_PATH: reportPath }; 1237 | const vite = spawn("pnpm", ["run", "dev:web"], { cwd: spawnCwd, stdio: "inherit", shell: true, env: envForSpaw 1238 | const onExit = () => {

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

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

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

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

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

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

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

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

v0.9.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.

v0.9.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.

v0.9.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.

v0.9.2

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

v0.7.3

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

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

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

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

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

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

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

v0.4.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.

v0.4.3

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

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

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

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

v0.3.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.

v0.3.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.

v0.3.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.

v0.3.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.

v0.3.3

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

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

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

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

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

v0.1.3

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

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

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.