Skip to content

Codex Security 0.5.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 20 Oct 19:00
· 74 commits to main since this release
Immutable release. Only release title and notes can be modified.
npm-v0.5.1
b2fa515
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Highlights

Codex Security 0.5.1 adds hosted patch generation and fix verification, and improves saved-scan replay, Deep Scan recovery, and Windows setup.

  • Hosted patching and verification. Integrations can generate patches and independently verify candidate fixes through runHostedRemediation() and its JSON-RPC adapter using a supplied executor. Hosts own checkout isolation, sandbox enforcement, candidate patch identity, and publication. See the hosted remediation guide. (#1684)
  • Saved scan settings. Daybreak selections persist across scans and remediation, including fresh and resumed Deep Scan workers. Saved Bedrock scans retain the effective AWS region and profile, and inline patches preserve the selected profile's provider settings. Severity classification uses the saved repository to select helpers. (#1740, #1811, #1810, #1815)
  • Deep Scan recovery and progress. Reports retain accepted worker coverage and its original evidence, including coverage recovered after cancellation or a discovery deadline. Standard and diff scans refresh phase and review counts from saved state even when the model emits no new progress markers. (#1593, #1757)
  • Windows setup. Runtime preparation uses private workspaces in the state directory so elevated-sandbox permissions on TEMP do not prevent scans from starting. Policy generation supports the default elevated Windows sandbox; see the access details below. Update notices also recognize global installations managed by nvm-windows. (#1803, #1741, #1801)
  • Reliable command results. Optional logging, update notices, and scratch cleanup no longer override completed scan, import, or publication outcomes. Failed commands do not print success output, and patch and verification commands wait for required output writes to finish. (#1800, #1818, #1824, #1826, #1775, #1777)
Other fixes
  • Saved scopes, component scans, CSV imports, and activity displays preserve literal paths. Helper values beginning with - and literal TOML strings retain their values. (#1812, #1814, #1786, #1827, #1809, #1792)
  • Basic patching supports Git repositories before their first commit. Directory inventories exclude .svn metadata, and component scans include tracked files matched by .gitignore. (#1552, #1768)
  • Scan history, feedback selection, and automatic matching consistently use scan start times when choosing and comparing results. (#1772, #1774, #1776, #1779)
  • SARIF exports preserve sealed scan artifacts. CSV processing preserves large quoted fields and finalized Deep Scan candidate metadata. (#1769, #1785, #1828)
  • Canceled fix verification restores an already applied patch's state. Deduplication reviews retry temporary Codex rate-limit errors, and cancellation is honored around embedding callbacks and saved result writes. (#1819, #1767, #1789, #1821)
  • Runtime telemetry preserves analytics and OpenTelemetry controls across workers and remediation. (#1691)
  • Release automation waits for npm, installed-package checks, the GitHub Action, and container publication. Containers retain their place in the publication queue. (#1796, #1806)

Upgrade notes

Windows policy generation

With the elevated Windows sandbox, policy generation can read other local source, including sibling components. The policy prompt retains the selected component's scope. Credential, configuration, and Git metadata denials, read-only access, and disabled network access remain enforced. Explicit sandbox choices and Unix read scope are unchanged. (#1741)

Saved scans of SVN working copies

Directory scans and patch identities now exclude .svn metadata. If a saved scan or patch included that metadata and no longer matches its source, restart the scan or regenerate the patch. Git diff and working-tree scans still require Git. (#1552)

Custom component and CSV scan clients

Custom component clients and clients handling explicit CSV scopes now receive absolute scan targets. Component callers intentionally using home shorthand should supply an absolute path inside the repository. Saved plans and receipts retain their existing formats, and completed campaign receipts remain reusable. (#1814)

GitHub Action

The Marketplace display name is now OpenAI Codex Security. Use openai/codex-security@action-v0.5.1, or pin the full distribution commit recorded in the Action release manifest. The npm package name remains @openai/codex-security. Marketplace publication is a separate step after the automated release. (#1797)

Upgrading from earlier releases

If upgrading from before 0.5.0, also review the 0.5.0 upgrade notes, including custom capability-preflight integrations and selected-profile approval settings.

If upgrading from before 0.4.0, upgrade CLI and plugin installations together when they share a Codex Security state directory. The shared issue-history migration preserves existing Linear receipts, but older publishers cannot write to the migrated database. (#1426)

All changes

What's Changed

Features

Fixes

Other changes

  • chore(deps): update Zod to 4.6.7 by @dependabot[bot] in #1816
  • chore(deps): bump hono from 4.13.10 to 4.13.13 in /evals/triage-finding by @dependabot[bot] in #1832

New Contributors

Full Changelog: npm-v0.5.0...npm-v0.5.1

Contributors

sylvesterkaczmarek, dependabot, and 6 other contributors
Assets 4
Loading