@vibe-forge/adapter-copilot
GitHub Copilot CLI Adapter for Vibe Forge
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Adapter merges process.env with override keys to pass to subprocess — standard proxy adapter pattern, not exfiltration. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP (127.0.0.1) appears only in test files for local test server setup — not production code. | ai | |
| phantom-deps | phantom-dep:@github/copilot | AI (phantom-deps): @github/copilot is a declared runtime dependency in package.json; phantom-dep heuristic false positive for config-referenced deps. | ai |
v3.3.1
2 findingsSpreading entire process.env into an object — may capture all secrets 81 | } 82 | > 83 | export const toProcessEnv = (env: AdapterCtx['env']): NodeJS.ProcessEnv => ({ 84 | ...process.env, 85 | ...Object.fromEntries(
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
2 findingsSpreading entire process.env into an object — may capture all secrets 86 | } 87 | > 88 | export const toProcessEnv = (env: AdapterCtx['env']): NodeJS.ProcessEnv => ({ 89 | ...process.env, 90 | ...Object.fromEntries(
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
2 findingsSpreading entire process.env into an object — may capture all secrets 84 | } 85 | > 86 | export const toProcessEnv = (env: AdapterCtx['env']): NodeJS.ProcessEnv => ({ 87 | ...process.env, 88 | ...Object.fromEntries(
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.