@agentuity/opencode — Greenflagged

Agentuity Open Code plugin with specialized AI coding agents

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

p0tofpiehuijirojhaynie

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/agents/product.d.ts	AI (source-diff): Same pattern: exported string constant with markdown/code content in a .d.ts file.	ai	2026/05/26
source-diff	obfuscated-file:dist/agents/expert-backend.d.ts	AI (source-diff): Same pattern: exported string constant with markdown/code content in a .d.ts file.	ai	2026/05/26
source-diff	obfuscated-file:dist/agents/expert-frontend.d.ts	AI (source-diff): Same pattern: exported string constant with markdown/code content in a .d.ts file.	ai	2026/05/26
source-diff	obfuscated-file:dist/agents/expert-ops.d.ts	AI (source-diff): Same pattern: exported string constant with markdown/code content in a .d.ts file.	ai	2026/05/26
source-diff	obfuscated-file:dist/agents/architect.d.ts	AI (source-diff): Long lines are AI system prompt strings in TypeScript declaration files, not obfuscated code.	ai	2026/05/21
source-diff	obfuscated-file:dist/agents/planner.d.ts	AI (source-diff): Long lines are AI system prompt strings in TypeScript declaration files, not obfuscated code.	ai	2026/05/21
source-diff	obfuscated-file:dist/agents/runner.d.ts	AI (source-diff): Long lines are AI system prompt strings in TypeScript declaration files, not obfuscated code.	ai	2026/05/21
semgrep	semgrep:env-spread	AI (semgrep): Intentional subprocess env passthrough pattern; standard for agent/plugin packages that spawn child processes.	ai	2026/05/17

Versions (showing 100 of 108)

Version	Deps	Published
3.0.4	4 / 4	2026-06-03
3.0.3	4 / 4	2026-06-01
3.0.2	4 / 4	2026-05-29
3.0.1	4 / 4	2026-05-26
3.0.0	4 / 4	2026-05-25
2.0.21	4 / 4	2026-05-13
2.0.20	4 / 4	2026-05-13
2.0.19	4 / 4	2026-05-12
2.0.18	4 / 4	2026-05-12
2.0.17	4 / 4	2026-05-09
2.0.16	4 / 4	2026-05-07
2.0.15	4 / 4	2026-05-06
2.0.14	4 / 4	2026-05-04
2.0.13	4 / 4	2026-05-02
2.0.12	4 / 4	2026-04-28
2.0.11	4 / 4	2026-04-08
2.0.10	4 / 4	2026-04-03
2.0.8	4 / 4	2026-04-03
2.0.7	4 / 4	2026-03-31
2.0.6	4 / 4	2026-03-30
2.0.5	4 / 4	2026-03-29
2.0.4	4 / 4	2026-03-29
2.0.3	4 / 4	2026-03-29
2.0.2	4 / 4	2026-03-29
2.0.1	4 / 4	2026-03-28
2.0.0	4 / 4	2026-03-27
1.0.64	4 / 4	2026-03-29
1.0.63	4 / 4	2026-03-27
1.0.62	4 / 4	2026-03-27
1.0.60	4 / 4	2026-03-26
1.0.59	4 / 4	2026-03-25
1.0.58	4 / 4	2026-03-25
1.0.57	4 / 4	2026-03-25
1.0.56	4 / 4	2026-03-24
1.0.55	4 / 4	2026-03-24
1.0.54	4 / 4	2026-03-20
1.0.52	4 / 4	2026-03-19
1.0.51	4 / 4	2026-03-19
1.0.50	4 / 4	2026-03-19
1.0.49	4 / 4	2026-03-18
1.0.48	4 / 4	2026-03-18
1.0.47	4 / 4	2026-03-18
1.0.46	4 / 4	2026-03-17
1.0.45	4 / 4	2026-03-17
1.0.44	4 / 4	2026-03-17
1.0.43	4 / 4	2026-03-15
1.0.42	4 / 4	2026-03-14
1.0.41	4 / 4	2026-03-12
1.0.40	4 / 4	2026-03-10
1.0.39	4 / 4	2026-03-09
1.0.38	4 / 4	2026-03-07
1.0.37	4 / 4	2026-03-06
1.0.36	4 / 4	2026-03-06
1.0.35	4 / 4	2026-03-05
1.0.34	4 / 4	2026-03-04
1.0.33	4 / 4	2026-03-03
1.0.32	4 / 4	2026-03-03
1.0.31	4 / 4	2026-03-02
1.0.30	4 / 4	2026-03-02
1.0.29	4 / 4	2026-03-01
1.0.28	4 / 4	2026-03-01
1.0.27	4 / 4	2026-03-01
1.0.26	4 / 4	2026-02-28
1.0.25	4 / 4	2026-02-28
1.0.24	4 / 4	2026-02-26
1.0.23	4 / 4	2026-02-26
1.0.22	4 / 4	2026-02-25
1.0.21	4 / 4	2026-02-23
1.0.20	4 / 4	2026-02-23
1.0.19	4 / 4	2026-02-22
1.0.18	4 / 4	2026-02-22
1.0.17	4 / 4	2026-02-22
1.0.16	4 / 4	2026-02-22
1.0.15	4 / 4	2026-02-18
1.0.14	4 / 4	2026-02-16
1.0.13	4 / 4	2026-02-16
1.0.12	4 / 4	2026-02-13
1.0.11	4 / 4	2026-02-13
1.0.8	4 / 4	2026-02-12
1.0.7	4 / 4	2026-02-11
1.0.6	4 / 4	2026-02-10
0.1.41	4 / 4	2026-01-30
0.1.40	3 / 4	2026-01-30
0.1.39	3 / 4	2026-01-30
0.1.38	3 / 4	2026-01-28
0.1.37	2 / 4	2026-01-27
0.1.36	2 / 4	2026-01-27
0.1.35	2 / 4	2026-01-27
0.1.34	2 / 4	2026-01-27
0.1.33	2 / 4	2026-01-26
0.1.32	2 / 4	2026-01-25
0.1.31	2 / 4	2026-01-24
0.1.30	2 / 4	2026-01-23
0.1.29	2 / 4	2026-01-23
0.1.28	2 / 4	2026-01-23
0.1.27	2 / 4	2026-01-23
0.1.26	2 / 4	2026-01-22
0.1.25	2 / 4	2026-01-22
0.1.24	2 / 4	2026-01-21
0.1.23	2 / 4	2026-01-20

Showing 100 of 108 Next page →

v3.0.4

1 finding

LOW No provenance attestation provenance

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

v3.0.3

1 finding

LOW No provenance attestation provenance

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

v3.0.2

1 finding

LOW No provenance attestation provenance

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

v3.0.1

1 finding

LOW No provenance attestation provenance

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

v3.0.0

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: jhaynie → huijiro (on 2026-05-25, known maintainer) provenance

This version was published by a different npm account (huijiro) than the most recent previously approved version (jhaynie) on 2026-05-25, but huijiro 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.

v2.0.21

1 finding

LOW No provenance attestation provenance

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

v2.0.20

1 finding

LOW No provenance attestation provenance

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

v2.0.19

3 findings

HIGH env-spread: src/agents/memory/entities.ts:49 semgrep

Spreading entire process.env into an object — may capture all secrets 47 | stdout: 'pipe', 48 | stderr: 'pipe', > 49 | env: env ? { ...process.env, ...env } : undefined, 50 | }); 51 |

HIGH env-spread: src/plugin/plugin.ts:724 semgrep

Spreading entire process.env into an object — may capture all secrets 722 | stdout: 'pipe', 723 | stderr: 'pipe', > 724 | env: { 725 | ...process.env, 726 | AGENTUITY_PROFILE: profile,

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.

v2.0.18

3 findings

HIGH env-spread: src/agents/memory/entities.ts:49 semgrep

Spreading entire process.env into an object — may capture all secrets 47 | stdout: 'pipe', 48 | stderr: 'pipe', > 49 | env: env ? { ...process.env, ...env } : undefined, 50 | }); 51 |

HIGH env-spread: src/plugin/plugin.ts:724 semgrep

Spreading entire process.env into an object — may capture all secrets 722 | stdout: 'pipe', 723 | stderr: 'pipe', > 724 | env: { 725 | ...process.env, 726 | AGENTUITY_PROFILE: profile,

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.

v2.0.17

1 finding

LOW No provenance attestation provenance

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

v2.0.16

1 finding

LOW No provenance attestation provenance

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

v2.0.15

1 finding

LOW No provenance attestation provenance

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

v2.0.14

1 finding

LOW No provenance attestation provenance

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

v2.0.13

1 finding

LOW No provenance attestation provenance

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

v2.0.12

3 findings

HIGH env-spread: src/agents/memory/entities.ts:49 semgrep

Spreading entire process.env into an object — may capture all secrets 47 | stdout: 'pipe', 48 | stderr: 'pipe', > 49 | env: env ? { ...process.env, ...env } : undefined, 50 | }); 51 |

HIGH env-spread: src/plugin/plugin.ts:724 semgrep

Spreading entire process.env into an object — may capture all secrets 722 | stdout: 'pipe', 723 | stderr: 'pipe', > 724 | env: { 725 | ...process.env, 726 | AGENTUITY_PROFILE: profile,

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.

v2.0.11

1 finding

LOW No provenance attestation provenance

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

v2.0.10

3 findings

HIGH env-spread: src/agents/memory/entities.ts:49 semgrep

Spreading entire process.env into an object — may capture all secrets 47 | stdout: 'pipe', 48 | stderr: 'pipe', > 49 | env: env ? { ...process.env, ...env } : undefined, 50 | }); 51 |

HIGH env-spread: src/plugin/plugin.ts:724 semgrep

Spreading entire process.env into an object — may capture all secrets 722 | stdout: 'pipe', 723 | stderr: 'pipe', > 724 | env: { 725 | ...process.env, 726 | AGENTUITY_PROFILE: profile,

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.

v2.0.8

1 finding

LOW No provenance attestation provenance

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

v2.0.7

1 finding

LOW No provenance attestation provenance

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

v2.0.6

1 finding

LOW No provenance attestation provenance

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

v2.0.5

1 finding

LOW No provenance attestation provenance

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

v2.0.4

1 finding

LOW No provenance attestation provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

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

v1.0.64

1 finding

LOW No provenance attestation provenance

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

v1.0.63

1 finding

LOW No provenance attestation provenance

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

v1.0.62

1 finding

LOW No provenance attestation provenance

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

v1.0.60

1 finding

LOW No provenance attestation provenance

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

v1.0.59

1 finding

LOW No provenance attestation provenance

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

v1.0.58

1 finding

LOW No provenance attestation provenance

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

v1.0.57

1 finding

LOW No provenance attestation provenance

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

v1.0.56

1 finding

LOW No provenance attestation provenance

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

v1.0.55

1 finding

LOW No provenance attestation provenance

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

v1.0.54

1 finding

LOW No provenance attestation provenance

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

v1.0.52

1 finding

LOW No provenance attestation provenance

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

v1.0.51

1 finding

LOW No provenance attestation provenance

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

v1.0.50

1 finding

LOW No provenance attestation provenance

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

v1.0.49

1 finding

LOW No provenance attestation provenance

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

v1.0.48

1 finding

LOW No provenance attestation provenance

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

v1.0.47

1 finding

LOW No provenance attestation provenance

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

v1.0.46

1 finding

LOW No provenance attestation provenance

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

v1.0.45

1 finding

LOW No provenance attestation provenance

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

v1.0.44

1 finding

LOW No provenance attestation provenance

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

v1.0.43

1 finding

LOW No provenance attestation provenance

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

v1.0.42

1 finding

LOW No provenance attestation provenance

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

v1.0.41

1 finding

LOW No provenance attestation provenance

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

v1.0.40

1 finding

LOW No provenance attestation provenance

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

v1.0.39

1 finding

LOW No provenance attestation provenance

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

v1.0.38

1 finding

LOW No provenance attestation provenance

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

v1.0.37

1 finding

LOW No provenance attestation provenance

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

v1.0.36

1 finding

LOW No provenance attestation provenance

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

v1.0.35

3 findings

HIGH env-spread: src/agents/memory/entities.ts:49 semgrep

Spreading entire process.env into an object — may capture all secrets 47 | stdout: 'pipe', 48 | stderr: 'pipe', > 49 | env: env ? { ...process.env, ...env } : undefined, 50 | }); 51 |

HIGH env-spread: src/plugin/plugin.ts:724 semgrep

Spreading entire process.env into an object — may capture all secrets 722 | stdout: 'pipe', 723 | stderr: 'pipe', > 724 | env: { 725 | ...process.env, 726 | AGENTUITY_PROFILE: profile,

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

1 finding

LOW No provenance attestation provenance

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

v1.0.33

1 finding

LOW No provenance attestation provenance

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

v1.0.32

1 finding

LOW No provenance attestation provenance

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

v1.0.31

1 finding

LOW No provenance attestation provenance

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

v1.0.30

1 finding

LOW No provenance attestation provenance

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

v1.0.29

1 finding

LOW No provenance attestation provenance

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

v1.0.28

1 finding

LOW No provenance attestation provenance

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

v1.0.27

1 finding

LOW No provenance attestation provenance

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

v1.0.26

1 finding

LOW No provenance attestation provenance

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

v1.0.25

1 finding

LOW No provenance attestation provenance

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

v1.0.24

1 finding

LOW No provenance attestation provenance

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

v1.0.23

1 finding

LOW No provenance attestation provenance

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

v1.0.22

1 finding

LOW No provenance attestation provenance

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

v1.0.21

1 finding

LOW No provenance attestation provenance

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

v1.0.20

1 finding

LOW No provenance attestation provenance

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

v1.0.19

1 finding

LOW No provenance attestation provenance

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

v1.0.18

1 finding

LOW No provenance attestation provenance

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

v1.0.17

1 finding

LOW No provenance attestation provenance

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

v1.0.16

1 finding

LOW No provenance attestation provenance

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

v1.0.15

1 finding

LOW No provenance attestation provenance

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

v1.0.14

1 finding

LOW No provenance attestation provenance

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

v1.0.13

1 finding

LOW No provenance attestation provenance

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

v1.0.12

1 finding

LOW No provenance attestation provenance

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

v1.0.11

3 findings

HIGH env-spread: src/agents/memory/entities.ts:49 semgrep

Spreading entire process.env into an object — may capture all secrets 47 | stdout: 'pipe', 48 | stderr: 'pipe', > 49 | env: env ? { ...process.env, ...env } : undefined, 50 | }); 51 |

HIGH env-spread: src/plugin/plugin.ts:830 semgrep

Spreading entire process.env into an object — may capture all secrets 828 | stdout: 'pipe', 829 | stderr: 'pipe', > 830 | env: { 831 | ...process.env, 832 | AGENTUITY_PROFILE: profile,

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

7 findings

HIGH New obfuscated file: dist/agents/architect.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/agents/expert-backend.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/agents/expert-frontend.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/agents/expert-ops.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/agents/product.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/agents/runner.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.0.7