Skip to content

OpenAI's Codex Security CLI and TypeScript SDK for finding, validating, and fixing security vulnerabilities. npm: https://www.npmjs.com/package/@openai/codex-security

chore(codex-security): sync public projection

mldangelo-oai7a4110f7c8f1
diff --git a/sdk/typescript/_bundled_plugin/references/scan-contract.md b/sdk/typescript/_bundled_plugin/references/scan-contract.md
index 16b97271c..307975423 100644
--- a/sdk/typescript/_bundled_plugin/references/scan-contract.md
+++ b/sdk/typescript/_bundled_plugin/references/scan-contract.md
@@ -10,11 +10,7 @@ A completed semantic bundle contains these files under `<scan_dir>`:
- `findings.json`: semantic finding records for the completed scan
- `coverage.json`: structured coverage summary with detailed receipt references
-Canonical UTF-8 document sizes are bounded consistently by the producer and SDK:
-`scan-manifest.json` is limited to 16 MiB, `findings.json` to 128 MiB, and
-`coverage.json` to 32 MiB. Finalization rejects oversized inputs or generated
-documents before sealing or changing scan outputs. Keep detailed evidence in
-scan-local artifacts and reference it from the canonical summaries.
+Canonical UTF-8 document sizes are bounded consistently by the producer and SDK: `scan-manifest.json` is limited to 16 MiB, `findings.json` to 128 MiB, and `coverage.json` to 32 MiB. Finalization rejects oversized inputs or generated documents before sealing or changing scan outputs. Keep detailed evidence in scan-local artifacts and reference it from the canonical summaries.
Optional structured finding details used by rich consumers are documented in `finding-detail-fields.md`. They remain part of each semantic finding record, not a projection parsed from a readable report.