@mmmbuto/codex-vl
Optimized version of OpenAI Codex for side-by-side installs, loop-driven workflows, and Vivling companions
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): env-spread in codex-exec.js is a standard pattern for passing environment to child processes in CLI tools; not a standalone risk signal. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.137.0 | 0 / 0 | |
| 0.136.2 | 0 / 0 | |
| 0.136.1 | 0 / 0 | |
| 0.136.0 | 0 / 0 | |
| 0.135.0 | 0 / 0 | |
| 0.134.1 | 0 / 0 | |
| 0.134.0 | 0 / 0 | |
| 0.133.0 | 0 / 0 | |
| 0.132.0 | 0 / 0 | |
| 0.131.0 | 0 / 0 | |
| 0.130.0 | 0 / 0 | |
| 0.129.1 | 0 / 0 | |
| 0.129.0 | 0 / 0 | |
| 0.128.5 | 0 / 0 | |
| 0.128.4 | 0 / 0 | |
| 0.128.2 | 0 / 0 | |
| 0.128.1 | 0 / 0 | |
| 0.128.0 | 0 / 0 | |
| 0.125.0 | 0 / 0 | |
| 0.124.2 | 0 / 0 | |
| 0.124.1 | 0 / 0 | |
| 0.124.0 | 0 / 0 |
v0.137.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.136.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.136.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.136.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.135.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.134.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.134.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.133.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.132.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.131.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.130.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.129.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.129.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.128.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.128.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.128.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.128.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.128.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.125.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.124.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.124.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.124.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.