@vibe-forge/adapter-opencode
OpenCode 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 spawns child processes; spreading process.env with caller overrides is the documented pattern for subprocess env construction. | ai | |
| phantom-deps | phantom-dep:opencode-ai | AI (phantom-deps): opencode-ai is a declared runtime dependency; phantom-dep heuristic fires because it's referenced via config rather than direct import. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.3.0 | 7 / 0 | |
| 3.1.4 | 7 / 0 | |
| 0.1.4 | 2 / 0 | |
| 0.1.3 | 2 / 0 | |
| 0.1.2 | 2 / 0 |
v3.3.0
2 findingsSpreading entire process.env into an object — may capture all secrets 127 | cliModel, 128 | effort: effortConfig.effectiveEffort, > 129 | env: toProcessEnv({ 130 | ...process.env, 131 | ...params.ctx.env,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
2 findingsSpreading entire process.env into an object — may capture all secrets 127 | cliModel, 128 | effort: effortConfig.effectiveEffort, > 129 | env: toProcessEnv({ 130 | ...process.env, 131 | ...params.ctx.env,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
2 findingsSpreading entire process.env into an object — may capture all secrets 98 | return { 99 | cliModel, > 100 | env: toProcessEnv({ 101 | ...process.env, 102 | ...params.ctx.env,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
2 findingsSpreading entire process.env into an object — may capture all secrets 68 | return { 69 | cliModel, > 70 | env: toProcessEnv({ 71 | ...process.env, 72 | ...params.ctx.env,
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 68 | return { 69 | cliModel, > 70 | env: toProcessEnv({ 71 | ...process.env, 72 | ...params.ctx.env,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.