---
title: "Codex Security GitHub Action releases version 0.10.1"
id: "story-81"
canonical_url: "https://emergent.fm/stories/81"
markdown_url: "https://emergent.fm/stories/81/article.md"
published_at: "2026-11-20T22:16:16.936Z"
modified_at: "2026-11-20T22:23:04.132Z"
topic: "coding_agents"
trust_label: "Reported"
publisher: "Emergent.FM"
---

# Codex Security GitHub Action releases version 0.10.1

> Codex Security GitHub Action ships as an immutable release where only the title and notes can change.

## Key points

- OpenAI released Codex Security GitHub Action 0.10.1 on 18 November as an immutable release that installs @openai/codex-security@0.10.1.
- The documented GitHub Actions workflow runs weekly scans on GitHub-hosted Ubuntu using the CODEX_SECURITY_API_KEY repository secret and a pinned commit SHA.
- The Marketplace listing says the example workflow sets an estimated $5 limit per scan and reports findings without failing the job, though requests in progress can exceed that limit.

OpenAI published Codex Security GitHub Action 0.10.1 on 18 November 2026, packaging the @openai/codex-security@0.10.1 release for automated workflows, according to the GitHub release page. The release is marked immutable, so only the release title and notes can be modified after publication. Alongside the source archives, the release page includes a 1.83 KB release manifest, a 105 KB CycloneDX software bill of materials, and a release attestation file.

## What changed in version 0.10.1

The underlying Codex Security 0.10.1 package, also released on 18 November, adds path exclusions for Standard, Deep, and diff scans, according to its release notes. Builders can pass --exclude-path or set scan.exclude_paths in project configuration so the scanner still reads excluded files for context while filtering out findings located only under those paths. The release notes also state that Deep Scan now stops and reports a refusal without retrying when Codex blocks a worker request for a misalignment policy violation.

## How to set up the GitHub Action

To run a weekly repository scan on GitHub-hosted Ubuntu, the Marketplace guide instructs builders to store an OpenAI API key in the repository secret CODEX_SECURITY_API_KEY. Teams then copy the example weekly workflow to .github/workflows/codex-security.yml and replace the commit placeholder with the reviewed distribution commit SHA. The 0.10.1 release page lists that SHA as bf650710f36c16936324efe250a49cdd9f2da037. Builders can trigger a run immediately from the Actions tab before the next scheduled scan.

## What the action outputs and requires

According to the Marketplace listing, the action scans code, enforces findings policy, and produces JSON and SARIF reports. For local CLI usage, the documentation specifies Node.js 22.13.0+ within 22.x, or Node.js 24.x or 26.x, alongside Python 3.10+, with tomli required on Python 3.10. Scans also support Amazon Bedrock using AWS credentials, as well as OpenRouter, Fireworks AI, and Cheaper Inference.

## Cost limits and access constraints

The Marketplace documentation notes that the example workflow uses an estimated $5 limit per scan and reports findings without failing the job, while warning that requests in progress can exceed that limit. Some cybersecurity requests and protected findings require Trusted Access for Cyber, according to the guide. GitHub also notes on the listing that OpenAI Codex Security is not certified by GitHub and is governed by separate third-party terms.

## Sources

- [Codex Security GitHub Action 0.10.1](<https://github.com/openai/codex-security/releases/tag/action-v0.10.1>) (github.com/openai, 2026-11-18, release)
- [Codex Security](<https://github.com/marketplace/actions/openai-codex-security>) (github.com/marketplace, documentation)
- [Codex Security 0.10.1](<https://github.com/openai/codex-security/releases/tag/npm-v0.10.1>) (github.com/openai, 2026-11-18, release)

Canonical page: <https://emergent.fm/stories/81>
