@agentuity/opencode
Agentuity Open Code plugin with specialized AI coding agents
Supply chain provenance
Status for the latest visible version.
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
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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 | |
| semgrep | semgrep:env-spread | AI (semgrep): Intentional subprocess env passthrough pattern; standard for agent/plugin packages that spawn child processes. | ai |
Versions (showing 51 of 108)
| Version | Deps | Published |
|---|---|---|
| 3.0.4 | 4 / 4 | |
| 3.0.3 | 4 / 4 | |
| 3.0.2 | 4 / 4 | |
| 3.0.1 | 4 / 4 | |
| 3.0.0 | 4 / 4 | |
| 2.0.21 | 4 / 4 | |
| 2.0.20 | 4 / 4 | |
| 2.0.19 | 4 / 4 | |
| 2.0.18 | 4 / 4 | |
| 2.0.17 | 4 / 4 | |
| 2.0.16 | 4 / 4 | |
| 2.0.15 | 4 / 4 | |
| 2.0.14 | 4 / 4 | |
| 2.0.13 | 4 / 4 | |
| 2.0.12 | 4 / 4 | |
| 2.0.11 | 4 / 4 | |
| 2.0.10 | 4 / 4 | |
| 2.0.8 | 4 / 4 | |
| 2.0.7 | 4 / 4 | |
| 2.0.6 | 4 / 4 | |
| 2.0.5 | 4 / 4 | |
| 2.0.4 | 4 / 4 | |
| 2.0.3 | 4 / 4 | |
| 2.0.2 | 4 / 4 | |
| 2.0.1 | 4 / 4 | |
| 2.0.0 | 4 / 4 | |
| 1.0.64 | 4 / 4 | |
| 1.0.63 | 4 / 4 | |
| 1.0.62 | 4 / 4 | |
| 1.0.60 | 4 / 4 | |
| 1.0.59 | 4 / 4 | |
| 1.0.58 | 4 / 4 | |
| 1.0.57 | 4 / 4 | |
| 1.0.56 | 4 / 4 | |
| 1.0.55 | 4 / 4 | |
| 1.0.54 | 4 / 4 | |
| 1.0.52 | 4 / 4 | |
| 1.0.51 | 4 / 4 | |
| 1.0.50 | 4 / 4 | |
| 1.0.49 | 4 / 4 | |
| 1.0.48 | 4 / 4 | |
| 1.0.47 | 4 / 4 | |
| 1.0.46 | 4 / 4 | |
| 1.0.45 | 4 / 4 | |
| 1.0.44 | 4 / 4 | |
| 1.0.43 | 4 / 4 | |
| 1.0.42 | 4 / 4 | |
| 1.0.41 | 4 / 4 | |
| 1.0.40 | 4 / 4 | |
| 1.0.39 | 4 / 4 | |
| 1.0.38 | 4 / 4 |
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.19
3 findingsSpreading 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 |
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,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.18
3 findingsSpreading 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 |
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,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
3 findingsSpreading 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 |
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,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
3 findingsSpreading 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 |
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,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.