@vibe-forge/adapter-codex
Codex App Server 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@openai/codex | AI (phantom-deps): @openai/codex is a declared runtime dep used as a spawned CLI binary, not a direct import — phantom-dep heuristic is a stable false positive here. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Used in buildSpawnEnv to pass env to child processes — standard adapter pattern, not exfiltration. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP is 127.0.0.1 (localhost) for local proxy server binding — not a suspicious remote endpoint. | ai |
v3.4.0
3 findingsSpreading entire process.env into an object — may capture all secrets 174 | } 175 | > 176 | const buildSpawnEnv = (env: AdapterCtx['env']): NodeJS.ProcessEnv => ({ 177 | ...process.env, 178 | ...Object.fromEntries(
Spreading entire process.env into an object — may capture all secrets 42 | 43 | function buildSpawnEnv(env: AdapterCtx['env']): NodeJS.ProcessEnv { > 44 | return { 45 | ...process.env, 46 | ...Object.fromEntries(
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
3 findingsSpreading entire process.env into an object — may capture all secrets 170 | } 171 | > 172 | const buildSpawnEnv = (env: AdapterCtx['env']): NodeJS.ProcessEnv => ({ 173 | ...process.env, 174 | ...Object.fromEntries(
Spreading entire process.env into an object — may capture all secrets 45 | 46 | function buildSpawnEnv(env: AdapterCtx['env']): NodeJS.ProcessEnv { > 47 | return { 48 | ...process.env, 49 | ...Object.fromEntries(
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.8
2 findingsSpreading entire process.env into an object — may capture all secrets 36 | 37 | function buildSpawnEnv(env: AdapterCtx['env']): NodeJS.ProcessEnv { > 38 | return { 39 | ...process.env, 40 | ...Object.fromEntries(
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 32 | 33 | function buildSpawnEnv(env: AdapterCtx['env']): NodeJS.ProcessEnv { > 34 | return { 35 | ...process.env, 36 | ...Object.fromEntries(
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.