packaged by Chainguard
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
Codex Security CLI that scans source repositories for vulnerabilities with OpenAI's Codex agent
Chainguard Containers are regularly-updated, secure-by-default container images.
For those with access, this container image is available on cgr.dev:
Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.
The codex-security image provides a containerized version of OpenAI's Codex Security, a CLI that scans source repositories for vulnerabilities by having the Codex agent investigate, validate, and report findings. It is built with Node.js and a small Rust native addon, and is licensed under Apache-2.0.
Compared to the upstream ghcr.io/openai/codex-security image, this image:
/usr/bin/codex) from source instead of shipping prebuilt binariescodex package, which can be newer than the @openai/codex version the scanner pins. codex-security info reports that pinned version as codexVersion, and scan records store it, while /usr/bin/codex --version shows the engine that actually runs/usr/local/bin/codex-security-entrypoint and default command --help, and the upstream /usr/local/bin/codex-security and /usr/local/bin/cs paths, so upstream's docker run and Compose invocations, including its seccomp profile, work unchangedcodex-security user (UID and GID 10001) with /state as the working directory, matching upstreamgit, openssh-client, python3, and Bubblewrap, which the scanner uses at runtimeThe image sets HOME and CODEX_HOME to /state, and CODEX_SECURITY_STATE_DIR to /output/.codex-security-state. Mount host directories at /output and /state that the container user can write to: UID 10001 by default, or your host user when you pass --user "$(id -u):$(id -g)" as the examples below do. Mount repositories to scan read-only under /input.
Codex runs scan commands inside a Bubblewrap sandbox, which needs user namespaces. Under Docker, run scans with a seccomp profile that allows the namespace system calls, such as the profile upstream provides. Dry runs and other commands don't need it.
Repositories mounted under /input can be owned by any user for repository and path scans. Git diff targets (--diff and --working-tree) run Git commands that refuse a repository owned by a different user ("dubious ownership"), as in the upstream image. For those targets, run the container with --user set to the owner of the checkout, or add a safe.directory entry to /state/.gitconfig.
Print the CLI help, which is the default command:
Preview what a scan of a local repository would cover without contacting a model provider:
Run a scan and write the report, findings, and SARIF output to a host directory. As in upstream's Compose runner, --user runs the container as your host user so it can write to the results and state directories you create:
Scan many repositories listed in a CSV file with bulk-scan. In this image, bulk-scan requires a CSV path because interactive repository discovery is not supported:
OPENAI_API_KEY or CODEX_API_KEY: credentials for the model provider.GH_TOKEN or GITHUB_TOKEN: when set, the entrypoint configures Git to use the bundled credential helper for HTTPS clones from CODEX_SECURITY_GIT_HOST (default github.com) and rewrites git@<host>: URLs to HTTPS.CODEX_SECURITY_STATE_DIR: location of saved scan history (default /output/.codex-security-state).The image exposes no ports and declares no volumes. Upstream's Compose files mount /input, /output, and /state at runtime.
Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.
All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.
The main features of Chainguard Containers include:
For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.
In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.
Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.
To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.
To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.
Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.
This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.
Chainguard's container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementChainguard Containers are SLSA Level 3 compliant with detailed metadata and documentation about how it was built. We generate build provenance and a Software Bill of Materials (SBOM) for each release, with complete visibility into the software supply chain.
SLSA compliance at ChainguardThis image helps reduce time and effort in establishing PCI DSS 4.0 compliance with low-to-no CVEs.
PCI DSS at Chainguard