* chore(deps): bump the codex group across 3 directories with 2 updates
Bumps the codex group with 1 update in the /evals/triage-finding directory: [@openai/codex-sdk](https://github.com/openai/codex/tree/HEAD/sdk/typescript).
Bumps the codex group with 1 update in the /plugins/codex-security/mcp-app directory: [@openai/codex-sdk](https://github.com/openai/codex/tree/HEAD/sdk/typescript).
Bumps the codex group with 2 updates in the /sdk/typescript directory: [@openai/codex-sdk](https://github.com/openai/codex/tree/HEAD/sdk/typescript) and [@openai/codex](https://github.com/openai/codex/tree/HEAD/codex-cli).
Updates `@openai/codex-sdk` from 0.170.0 to 0.171.0
Updates `@openai/codex-sdk` from 0.170.0 to 0.171.0
Updates `@openai/codex-sdk` from 0.170.0 to 0.171.0
Updates `@openai/codex` from 0.170.0 to 0.171.0
---
updated-dependencies:
- dependency-name: "@openai/codex-sdk"
dependency-version: 0.171.0
dependency-type: direct:production
update-type: version-update:semver-minor
dependency-group: codex
- dependency-name: "@openai/codex-sdk"
dependency-version: 0.171.0
dependency-type: direct:production
update-type: version-update:semver-minor
dependency-group: codex
- dependency-name: "@openai/codex-sdk"
dependency-version: 0.171.0
dependency-type: direct:production
update-type: version-update:semver-minor
dependency-group: codex
- dependency-name: "@openai/codex"
dependency-version: 0.171.0
dependency-type: direct:production
update-type: version-update:semver-minor
dependency-group: codex
...
Signed-off-by: dependabot[bot] <support@github.com>
* fix(container): record Codex 0.171.0 native source
---------
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Michael D'Angelo <mdangelo@openai.com>
Listing findings across linked worktrees could hang when a legacy
occurrence was appended to the group being iterated. Split each affected
group into fresh lists by repository generation or legacy target so
that each occurrence is visited once and dismissals stay local.
Cover both legacy and current group roots with the same saved history.
* feat(cli): add independently reviewed dependency checks
* Compare frozen Python advisory versions as releases
* fix(cli): bind unnamed root manifests to observed services
* test(cli): evaluate dependency investigations across public fixtures
* test(sdk): bound the budget wait after the mock scan starts
* test(cli): exercise MCP evidence and missing caller access
* Bind graded citations to the approved use evidence
* test: restore dependency investigation quality controls
* fix(cli): restore dependency investigation and report compatibility
* test: grade malformed dependency baseline answers
* fix(cli): scope headless tool access to the investigator
* test(cli): lock down reviewer and external evidence tool access
* fix(cli): keep linked evidence tied to its originating call
* Reconcile application mappings and expose original evidence hashes
* test: verify selected catalog rows against original replies
* fix(cli): recover incomplete reviews and preserve selected evidence rows
* fix(cli): preserve wire evidence and verify finding citations
* Finalize from approved submissions and explain remaining uses
* fix(cli): restore coordinator recovery, independent review and report contracts
* Review withdrawals under the original dependency assessment ID
* test(cli): compare trace progress with completed search scopes
* Recheck dependency coverage after concurrent investigation changes
* Preserve exploratory scope explanations during dependency review
* feat(cli): track shared source work in dependency investigations
* Include shared source work in final coverage checks
* Require deciding evidence on the caller it establishes
* Preserve generic MCP search outcomes and scopes in dependency reports
* Share pinned source notes between dependency investigators
* Ship the source worklist and search audit modules
* refactor(cli): name the dependency coordinator for its ability to resume
* refactor(cli): simplify the tools for dependency investigations
* fix(cli): keep investigation tool arguments visible to Codex and reuse the evidence store
* fix(cli): send missing verdict citations back to the reviewer
* fix(cli): verify caller bindings and input flow across investigation steps
* fix(cli): require direct citations for asserted runtime facts on every use
* test(cli): verify failed catalog lookups without a timed source scan
---------
Co-authored-by: utsav-oai <348536218+utsav-oai@users.noreply.github.com>
* chore(deps): bump the codex group across 3 directories with 2 updates
Bumps the codex group with 1 update in the /evals/triage-finding directory: [@openai/codex-sdk](https://github.com/openai/codex/tree/HEAD/sdk/typescript).
Bumps the codex group with 1 update in the /plugins/codex-security/mcp-app directory: [@openai/codex-sdk](https://github.com/openai/codex/tree/HEAD/sdk/typescript).
Bumps the codex group with 2 updates in the /sdk/typescript directory: [@openai/codex-sdk](https://github.com/openai/codex/tree/HEAD/sdk/typescript) and [@openai/codex](https://github.com/openai/codex/tree/HEAD/codex-cli).
Updates `@openai/codex-sdk` from 0.167.1 to 0.167.2
Updates `@openai/codex-sdk` from 0.167.1 to 0.167.2
Updates `@openai/codex-sdk` from 0.167.1 to 0.167.2
Updates `@openai/codex` from 0.167.1 to 0.167.2
---
updated-dependencies:
- dependency-name: "@openai/codex-sdk"
dependency-version: 0.167.2
dependency-type: direct:production
update-type: version-update:semver-patch
dependency-group: codex
- dependency-name: "@openai/codex-sdk"
dependency-version: 0.167.2
dependency-type: direct:production
update-type: version-update:semver-patch
dependency-group: codex
- dependency-name: "@openai/codex-sdk"
dependency-version: 0.167.2
dependency-type: direct:production
update-type: version-update:semver-patch
dependency-group: codex
- dependency-name: "@openai/codex"
dependency-version: 0.167.2
dependency-type: direct:production
update-type: version-update:semver-patch
dependency-group: codex
...
Signed-off-by: dependabot[bot] <support@github.com>
* fix(container): record the Wolfi source for Codex 0.167.2
---------
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Michael D'Angelo <mdangelo@openai.com>
Share each scan’s findings across bulk comparison batches. Preserve inline results for existing callers and resolve each batch before matching or saving it.
* test(plugin): apply saved patch bytes on Windows
* test(ci): provide ripgrep for the Windows MCP smoke test
* test(sdk): preserve env utility name in inventory fixture
(cherry picked from commit 5ce7e7c53c)
* test(plugin): make Deep Scan worker fixtures portable
* test(ci): exercise Deep Scan worker fixtures on Windows
* test(plugin): isolate worker PATH fixtures from the SDK
* test(plugin): format the worker search path fixture
* fix(plugin): preserve Windows helper exit codes
CMD expands %errorlevel% from an environment variable of that name before
the dynamic exit status, so an inherited ERRORLEVEL made the launcher
report stale helper results. Clear the variable before starting Node.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* Check inherited ERRORLEVEL through the documented Windows launcher
* fix(plugin): clear the inherited status variable only for helpers
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Co-authored-by: Michael D'Angelo <mdangelo@openai.com>
* feat(imports): import CrowdStrike FCS IaC findings locally
Add a crowdstrike file reader for saved FCS CLI 4.x IaC JSON reports
(rule_detections). Each detection becomes one iac or secret finding with
typed rule, configuration and remediation details. Like Tenable, the
reader is local only and binds findings to --source-repository-url,
which must match a fetch remote of the selected checkout.
FCS writes detection paths relative to its working directory, so the
guide asks users to scan from the checkout root. Paths that are absolute
or leave the checkout are excluded. The source finding ID includes the
line, because detections of one rule on one resource can differ only by
line.
* fix(imports): import CrowdStrike reports without a Git checkout
An FCS IaC report describes files relative to the directory where the CLI
ran and names no repository, so requiring a matching Git remote did not
bind the report to anything. Import into any directory instead, and check
that every detection's file exists there. A supplied
--source-repository-url still records the repository, adds typed details
and must match a fetch remote when the directory is a Git checkout.
Detections in registry or Git modules name the calling file with a line
from inside the module. Use the call line that FCS states in
module_remediation, or no line, and include the module path in the
finding ID.
* docs(plugin): describe CrowdStrike FCS imports in the publish-findings skill
Tell Codex when to use --provider crowdstrike, how to run an installed FCS CLI from the import directory, which report to import after a nonzero exit, and to ask for a report instead of installing FCS or passing Falcon credentials.
* fix(imports): read the CrowdStrike module call line in linear time
Search module_remediation for the detection file's exact call phrase instead of a lazy regex. A crafted report could make the regex quadratic: a 2 MB module_remediation took about two minutes to read.
* fix(imports): stop CrowdStrike imports when a scanned file changed
FCS records each scanned file's SHA-256 as file_sha256. Compare it with
the file in the selected directory and stop, naming the file, when they
differ. Before, a report of another commit imported without an error and
could store lines that no longer point at the detected configuration.
The check follows file symlinks, as FCS does, and reads only regular
files.
* docs(imports): add CrowdStrike scan examples and Codex validation steps
Fix the FCS scan command: FCS needs an existing output directory whose
name has no dot. Show a remote git:: scan pinned with ?ref= and a
checkout of the same commit, and note that a //subdir URL gives paths
from that subdirectory. Add a shortened sample report, and show how to
pass imported findings to codex-security validate, for all findings or
for one scan.
* docs(imports): link CrowdStrike imports to the shared imported finding workflow
Other provider pages do not describe validation or patching. Remove the
CrowdStrike validation section and link the readback step to the shared
section on working with imported findings.
* fix(imports): keep CrowdStrike module lines in git:: reports
In a git:: report, FCS writes the detection file, its module_source and
the calling file in module_remediation with a leading slash. The reader
removed the slash from the file before it compared the three, so every
module detection lost its line. Compare them as FCS wrote them. In a
git:: scan of a public Terraform repository, 102 of 396 findings had no
line before this change and none after.
* fix(imports): record and check the repository of CrowdStrike git:: reports
A git:: report names the repository that FCS cloned, but the reader
ignored it. A report of one repository could be saved under another one
whose files were identical. For a git::https:// scan, record that
repository without its //subdirectory and ?ref=, and keep the scan path
in the report and in each finding's source data. When
--source-repository-url is given, it must name the same repository, on
import and on replay. Without it, the scanned repository gives typed
details but does not bind the checkout to a fetch remote, so clones from
self-hosted servers over SSH keep importing. Other git:: URL forms
import as before.
* fix(imports): import CrowdStrike git:: reports of URLs with a user name
When the scanned URL has a user name, FCS writes each detection file,
module source and calling file after the scanned URL instead of after a
slash, and the reader excluded every detection. Remove that prefix. FCS
removes the user name and token from the report's path and keeps them
only in flags.path, which the reader does not read.
* fix(imports): check replayed CrowdStrike locations against the native detection
A replayed preview with cleared or edited locations skipped the file
check, and saved findings without the scanned location. Rebuild the
location from the retained FCS detection, require each finding to show
exactly that location, and check that file and its hash.
* feat(plugin): guide Codex through scanner acquisition and reviewed publication
* docs(plugin): name the stored publication calls and explain partial imports
* fix(cli): make saved scan selection and matching explicit
* fix(cli): resolve command paths and isolate standalone actions
* fix(cli): preserve updater result and diagnostics
* fix(cli): simplify finding imports and protect export files
* test(plugin): initialize Windows registration fixtures explicitly
* test(cli): distinguish the legacy publish check selector in help
* test(cli): check the requested JSON format in raw CSV diagnostics
* fix(cli): retain suggestions for unknown commands
* style(cli): format argument routing regressions
* test(cli): return worktree selection in authentication fixture
* fix(cli): reject missing global values before command dispatch
* fix(cli): preserve short help before a command
* fix(cli): reject switches as global option values
* fix(cli): identify package updates in generated agent guidance
* fix(cli): make saved scan selection and matching explicit
* test(plugin): initialize Windows registration fixtures explicitly
* test(cli): return worktree selection in authentication fixture
* Reuse workbench queries for first-time history readers
* Keep first-run database selection with history queries
* Initialize the index-plan fixture before inspecting SQLite
* Use the scoped history response in the implicit prompt rerun fixture
* chore(deps): bump the codex group across 3 directories with 2 updates
Bumps the codex group with 1 update in the /evals/triage-finding directory: [@openai/codex-sdk](https://github.com/openai/codex/tree/HEAD/sdk/typescript).
Bumps the codex group with 1 update in the /plugins/codex-security/mcp-app directory: [@openai/codex-sdk](https://github.com/openai/codex/tree/HEAD/sdk/typescript).
Bumps the codex group with 2 updates in the /sdk/typescript directory: [@openai/codex-sdk](https://github.com/openai/codex/tree/HEAD/sdk/typescript) and [@openai/codex](https://github.com/openai/codex/tree/HEAD/codex-cli).
Updates `@openai/codex-sdk` from 0.167.0 to 0.167.1
Updates `@openai/codex-sdk` from 0.167.0 to 0.167.1
Updates `@openai/codex-sdk` from 0.167.0 to 0.167.1
Updates `@openai/codex` from 0.167.0 to 0.167.1
---
updated-dependencies:
- dependency-name: "@openai/codex-sdk"
dependency-version: 0.167.1
dependency-type: direct:production
update-type: version-update:semver-patch
dependency-group: codex
- dependency-name: "@openai/codex-sdk"
dependency-version: 0.167.1
dependency-type: direct:production
update-type: version-update:semver-patch
dependency-group: codex
- dependency-name: "@openai/codex-sdk"
dependency-version: 0.167.1
dependency-type: direct:production
update-type: version-update:semver-patch
dependency-group: codex
- dependency-name: "@openai/codex"
dependency-version: 0.167.1
dependency-type: direct:production
update-type: version-update:semver-patch
dependency-group: codex
...
Signed-off-by: dependabot[bot] <support@github.com>
* fix(wolfi): record the source for the Codex 0.167.1 binary
---------
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Michael D'Angelo <mdangelo@openai.com>