@howaboua/pi-subagent-review
Pi extension that adds /review via an isolated review subagent.
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): Intentional child-process env passthrough with a single added var; standard subagent launcher pattern for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.2.3 | 0 / 5 | |
| 0.2.2 | 0 / 5 | |
| 0.2.1 | 0 / 5 | |
| 0.2.0 | 0 / 5 | |
| 0.1.53 | 0 / 5 | |
| 0.1.52 | 0 / 4 | |
| 0.1.51 | 0 / 4 | |
| 0.1.5 | 0 / 4 | |
| 0.1.4 | 0 / 4 | |
| 0.1.3 | 0 / 0 | |
| 0.1.2 | 0 / 0 | |
| 0.1.1 | 0 / 0 | |
| 0.1.0 | 0 / 0 |
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/IgorWarzocha/pi-subagent-review/blob/3c82418044408aa4961f74299e44a1efe198b13a/src/subagent.ts#L57 55 | shell: false, 56 | stdio: ["pipe", "pipe", "pipe"], > 57 | env: { ...process.env, [CHILD_ENV]: "1" }, 58 | }); 59 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/IgorWarzocha/pi-subagent-review/blob/5b4313d44aab2c3a1e4d83534c5a552965a1eac3/src/subagent.ts#L57 55 | shell: false, 56 | stdio: ["pipe", "pipe", "pipe"], > 57 | env: { ...process.env, [CHILD_ENV]: "1" }, 58 | }); 59 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/IgorWarzocha/pi-subagent-review/blob/e82a4f7a6b4fc91bad24389727516851bc4def19/src/subagent.ts#L57 55 | shell: false, 56 | stdio: ["pipe", "pipe", "pipe"], > 57 | env: { ...process.env, [CHILD_ENV]: "1" }, 58 | }); 59 |
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/IgorWarzocha/pi-subagent-review/blob/125ea2bb756e334caccaf4b2bde483e2e59c40c0/src/subagent.ts#L56 54 | shell: false, 55 | stdio: ["pipe", "pipe", "pipe"], > 56 | env: { ...process.env, [CHILD_ENV]: "1" }, 57 | }); 58 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.