Answer: To inspect repository history, open **Repositories** to browse available repositories and folders, then select a repository to inspect its scan history, latest scanned revision, and open findings. From repository details, you can open a previous scan or view the findings associated with that repository. Status: Confirmed Entry: tool/codex/permissions-and-security/inspect-repository-history Revision: 1 Digest: sha256:3684ee55d3c11649 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:53:47Z Last changed: 2026-11-13T03:53:47Z Last verified: 2026-11-20T13:42:19Z Next check: 2026-11-21T13:42:19Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Navigation step | Repositories | [1] | 2026-11-20 Repository details shown | scan history, latest scanned revision, and open findings | [1] | 2026-11-20 Action from repository details | open a previous scan or view the findings associated with that repository | [1] | 2026-11-20 If no scans | start a scan from its details or select **+ Scan** in the workbench | [1] | 2026-11-20 Sources: [1] OpenAI. "Use the Codex Security workbench". https://learn.chatgpt.com/docs/security/plugin/workbench.md Role: primary. Accessed: 2026-11-20T13:42:19Z Quote: "Open **Repositories** to browse available repositories and folders." (Supports: Navigation step) Quote: "Select a repository to inspect its scan history, latest scanned revision, and open findings." (Supports: Repository details shown) Quote: "From repository details, open a previous scan or view the findings associated with that repository." (Supports: Action from repository details) Quote: "If a repository has no scans, start a scan from its details or select **+ Scan** in the workbench." (Supports: If no scans) Snapshot SHA-256: 2f90053b15a0195a88a72a651cbfe574c5f52f750e7de88b740ed3cb496986f6 (captured 2026-11-13T03:53:45Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:53:47Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:42:19Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:42:19Z Last attempt: 2026-11-20T13:42:19Z Notes and limitations: Extracted automatically from a single official source (section "Inspect repository history"). Related: https://latestn.com/tool/codex/permissions-and-security/isolate-environment-cybersecurity How do I isolate the environment when running Codex for cybersecurity work? https://latestn.com/tool/codex/permissions-and-security/manage-privileges How do I manage privileges and permissions for the Codex GitHub Action? https://latestn.com/tool/codex/permissions-and-security/manual-security-review-of-changes How do I run a manual security review of code changes in Codex? https://latestn.com/tool/codex/permissions-and-security/gateway-authentication-methods Which authentication methods can Codex use to connect to a gateway? https://latestn.com/tool/codex/permissions-and-security/gateway-authentication-options What authentication options does a Codex gateway support? https://latestn.com/tool/codex/permissions-and-security/how-policies-combine How do Global, Local, and Codex Cloud policies combine in Codex Agent Security? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:53:47Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/permissions-and-security/inspect-repository-history/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/codex/permissions-and-security/inspect-repository-history POST: https://latestn.com/dispute/tool/codex/permissions-and-security/inspect-repository-history with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/permissions-and-security/inspect-repository-history?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I inspect repository history in the Codex Security workbench? Revision 1, last verified 2026-11-20T13:42:19Z. https://latestn.com/tool/codex/permissions-and-security/inspect-repository-history (accessed 2026-11-21T10:07:50Z). @misc{LatestN_tool_codex_permissions_and_security_inspect_repository_history_r1, title = {How do I inspect repository history in the Codex Security workbench?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/permissions-and-security/inspect-repository-history}}, note = {Revision 1; digest sha256:3684ee55d3c11649; last verified 2026-11-20T13:42:19Z; accessed 2026-11-21T10:07:50Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/codex/permissions-and-security/inspect-repository-history