@aiready/agents No license 46 versions

@aiready/agents

npm

Agentic remediation and analysis system for AIReady

46

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

caopeng

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@aiready/core	AI (phantom-deps): Same-org monorepo dep; declared but may be used transitively or via re-exports.	ai	2026/06/01
semgrep	semgrep:env-spread	AI (semgrep): MCP adapter legitimately merges process.env for subprocess spawning; not credential theft.	ai	2026/05/30
phantom-deps	phantom-dep:fast-glob	AI (phantom-deps): Referenced in config files per analyzer note; stable false positive for this package.	ai	2026/05/30
phantom-deps	phantom-dep:@ai-sdk/anthropic	AI (phantom-deps): Config-file reference pattern; stable false positive for this package.	ai	2026/05/30
phantom-deps	phantom-dep:@aiready/cli	AI (phantom-deps): Same-org scope dependency; stable false positive for this monorepo package.	ai	2026/05/30

Versions (showing 46 of 46)

Version	Deps	Published
0.4.28	12 / 4	2026-05-10
0.4.27	12 / 4	2026-05-05
0.4.26	12 / 4	2026-05-03
0.4.23	12 / 4	2026-04-29
0.4.22	12 / 4	2026-04-14
0.4.21	12 / 4	2026-04-12
0.4.20	9 / 4	2026-04-11
0.4.19	9 / 4	2026-04-08
0.4.18	9 / 4	2026-04-08
0.4.17	8 / 4	2026-04-07
0.4.16	8 / 4	2026-04-06
0.4.15	8 / 4	2026-04-06
0.4.14	8 / 4	2026-04-06
0.4.13	8 / 4	2026-04-06
0.4.12	8 / 4	2026-03-31
0.4.10	8 / 4	2026-03-29
0.4.9	8 / 4	2026-03-29
0.4.8	8 / 4	2026-03-29
0.4.7	8 / 4	2026-03-29
0.4.5	8 / 4	2026-03-28
0.4.4	8 / 4	2026-03-27
0.4.3	8 / 4	2026-03-27
0.4.2	8 / 4	2026-03-27
0.3.23	8 / 4	2026-03-25
0.3.22	7 / 4	2026-03-23
0.3.21	7 / 4	2026-03-23
0.3.20	7 / 3	2026-03-22
0.3.19	7 / 3	2026-03-22
0.3.18	7 / 3	2026-03-21
0.3.14	7 / 3	2026-03-21
0.3.13	7 / 3	2026-03-20
0.3.12	7 / 3	2026-03-20
0.3.11	7 / 3	2026-03-19
0.3.10	7 / 3	2026-03-19
0.3.9	7 / 3	2026-03-19
0.3.8	7 / 3	2026-03-19
0.3.7	7 / 3	2026-03-19
0.3.6	7 / 3	2026-03-17
0.3.5	4 / 3	2026-03-17
0.3.4	4 / 3	2026-03-15
0.3.3	4 / 3	2026-03-15
0.3.2	4 / 3	2026-03-14
0.3.1	4 / 3	2026-03-14
0.3.0	4 / 3	2026-03-14
0.2.0	4 / 3	2026-03-10
0.1.3	4 / 3	2026-03-09

v0.4.28

2 findings

HIGH env-spread: src/tools/mcp-adapter.ts:25 semgrep

Spreading entire process.env into an object — may capture all secrets 23 | command, 24 | args, > 25 | env: { ...process.env, ...env } as Record<string, string>, 26 | }); 27 |

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

1 finding

LOW No provenance attestation provenance

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

v0.4.26

1 finding

LOW No provenance attestation provenance

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

v0.4.23

1 finding

LOW No provenance attestation provenance

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

v0.4.22

1 finding

LOW No provenance attestation provenance

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

v0.4.21

1 finding

LOW No provenance attestation provenance

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

v0.4.20

1 finding

LOW No provenance attestation provenance

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

v0.4.19

1 finding

LOW No provenance attestation provenance

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

v0.4.18

1 finding

LOW No provenance attestation provenance

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

v0.4.17

1 finding

LOW No provenance attestation provenance

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

v0.4.16

1 finding

LOW No provenance attestation provenance

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

v0.4.15

2 findings

HIGH env-spread: src/tools/mcp-adapter.ts:25 semgrep

Spreading entire process.env into an object — may capture all secrets 23 | command, 24 | args, > 25 | env: { ...process.env, ...env } as Record<string, string>, 26 | }); 27 |

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

1 finding

LOW No provenance attestation provenance

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

v0.4.13

1 finding

LOW No provenance attestation provenance

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

v0.4.12

1 finding

LOW No provenance attestation provenance

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

v0.4.10

1 finding

LOW No provenance attestation provenance

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

v0.4.9

1 finding

LOW No provenance attestation provenance

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

v0.4.8

1 finding

LOW No provenance attestation provenance

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

v0.4.7

1 finding

LOW No provenance attestation provenance

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

v0.4.5

1 finding

LOW No provenance attestation provenance

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

v0.4.4

1 finding

LOW No provenance attestation provenance

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

v0.4.3

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.3.23

1 finding

LOW No provenance attestation provenance

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

v0.3.22

1 finding

LOW No provenance attestation provenance

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

v0.3.21

1 finding

LOW No provenance attestation provenance

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

v0.3.20

1 finding

LOW No provenance attestation provenance

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

v0.3.19

1 finding

LOW No provenance attestation provenance

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

v0.3.18

1 finding

LOW No provenance attestation provenance

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

v0.3.14

1 finding

LOW No provenance attestation provenance

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

v0.3.13

1 finding

LOW No provenance attestation provenance

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

v0.3.12

1 finding

LOW No provenance attestation provenance

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

v0.3.11

1 finding

LOW No provenance attestation provenance

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

v0.3.10

1 finding

LOW No provenance attestation provenance

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

v0.3.9

1 finding

LOW No provenance attestation provenance

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

v0.3.8

1 finding

LOW No provenance attestation provenance

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

v0.3.7

1 finding

LOW No provenance attestation provenance

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

v0.3.6

1 finding

LOW No provenance attestation provenance

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

v0.3.5

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

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