@agnishc/edb-claude-proxy
Pi extension: claude_proxy tool — delegate tasks to Claude Code CLI from within pi
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Spreading process.env into a child_process spawn call is the intended behavior for a CLI proxy delegating to Claude Code CLI. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.14.2 | 0 / 0 | |
| 0.14.0 | 0 / 0 | |
| 0.13.0 | 0 / 0 | |
| 0.12.0 | 0 / 0 | |
| 0.10.9 | 0 / 0 | |
| 0.10.8 | 0 / 0 | |
| 0.10.6 | 0 / 0 | |
| 0.10.5 | 0 / 0 | |
| 0.10.4 | 0 / 0 | |
| 0.10.3 | 0 / 0 | |
| 0.8.2 | 0 / 0 | |
| 0.8.1 | 0 / 0 | |
| 0.6.1 | 0 / 0 | |
| 0.5.1 | 0 / 0 | |
| 0.5.0 | 0 / 0 | |
| 0.4.0 | 0 / 0 | |
| 0.1.0 | 0 / 0 |
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.9
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/agnishcc/pi-extention-monorepo/blob/cba8b222567fbd57aca19e16b46396c1f132f11b/src/execute.ts#L79 77 | shell: false, 78 | stdio: ["pipe", "pipe", "pipe"], > 79 | env: { ...process.env }, 80 | }); 81 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.8
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/agnishcc/pi-extention-monorepo/blob/00afccfd6b66f03e09b305b64cda96dccb860912/src/execute.ts#L79 77 | shell: false, 78 | stdio: ["pipe", "pipe", "pipe"], > 79 | env: { ...process.env }, 80 | }); 81 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.6
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/agnishcc/pi-extention-monorepo/blob/de6ba82e29f11e7e75eb93eecf78979ae7029212/src/execute.ts#L79 77 | shell: false, 78 | stdio: ["pipe", "pipe", "pipe"], > 79 | env: { ...process.env }, 80 | }); 81 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.5
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/agnishcc/pi-extention-monorepo/blob/aa7634792b1d6f9bacbb219a341b3593648633c2/src/execute.ts#L79 77 | shell: false, 78 | stdio: ["pipe", "pipe", "pipe"], > 79 | env: { ...process.env }, 80 | }); 81 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/agnishcc/pi-extention-monorepo/blob/11873bb06857e420282f98f534d94b9951d4e6b7/src/execute.ts#L79 77 | shell: false, 78 | stdio: ["pipe", "pipe", "pipe"], > 79 | env: { ...process.env }, 80 | }); 81 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/agnishcc/pi-extention-monorepo/blob/0275be44847a878c1dd86cebe0f9bfe46c7f1b8f/src/execute.ts#L79 77 | shell: false, 78 | stdio: ["pipe", "pipe", "pipe"], > 79 | env: { ...process.env }, 80 | }); 81 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/agnishcc/pi-extention-monorepo/blob/50488b652908bd121dd8ac6844e060822caed25f/src/execute.ts#L79 77 | shell: false, 78 | stdio: ["pipe", "pipe", "pipe"], > 79 | env: { ...process.env }, 80 | }); 81 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/agnishcc/pi-extention-monorepo/blob/07d85a756054b335b15031be51af28f9b622a712/src/execute.ts#L79 77 | shell: false, 78 | stdio: ["pipe", "pipe", "pipe"], > 79 | env: { ...process.env }, 80 | }); 81 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/agnishcc/pi-extention-monorepo/blob/66ed2821dbbcd9f6db6d18a92960ff8aa8973d16/src/execute.ts#L79 77 | shell: false, 78 | stdio: ["pipe", "pipe", "pipe"], > 79 | env: { ...process.env }, 80 | }); 81 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/agnishcc/pi-extention-monorepo/blob/cf84e07b2791dc07607aa046e0651a5b51af1bdd/src/execute.ts#L79 77 | shell: false, 78 | stdio: ["pipe", "pipe", "pipe"], > 79 | env: { ...process.env }, 80 | }); 81 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/agnishcc/pi-extention-monorepo/blob/540f467dc90abfd912a7d0f35e804a0fef7e9e2b/src/execute.ts#L79 77 | shell: false, 78 | stdio: ["pipe", "pipe", "pipe"], > 79 | env: { ...process.env }, 80 | }); 81 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/agnishcc/pi-extention-monorepo/blob/91e03a14cb162db5272dd9ccd55cc11473be3514/src/execute.ts#L79 77 | shell: false, 78 | stdio: ["pipe", "pipe", "pipe"], > 79 | env: { ...process.env }, 80 | }); 81 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/agnishcc/pi-extention-monorepo/blob/d0d25df0a116b88dbdb1744216348ce11d576649/src/execute.ts#L79 77 | shell: false, 78 | stdio: ["pipe", "pipe", "pipe"], > 79 | env: { ...process.env }, 80 | }); 81 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.