updated 2026-10-11 04:08 UTC

Codex Bridge

Repository

Image generation (gpt-image-2) and GPT-5 subagents for Claude Code — through the Codex CLI login you already have. No OpenAI API key.

Agent Skills Shell Listed MIT

Is Codex Bridge safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.6 / 10
Provenance None
Signed commits 0%
Last push 62d ago
Compare Codex Bridge

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Codex Bridge scores 36.5/100 (Grade D), ranked #346 of 371 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.6/10; recent commits are unsigned; last pushed 2026-08-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Codex Bridge could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Codex Bridge and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Unsigned

    github.com/Sateezg/codex-bridge, MIT, last pushed 2026-08-10. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 2.6/10 (scanned Sep 19, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies -1
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 10

  3. Published packages None

    No registry package. Codex Bridge is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-08-30 OSSF Scorecard: 2.6/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Codex Bridge’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How Codex Bridge compares in Agent Skills

  1. #344 Brand Docs 36.6 +0.1
  2. #345 Arscontexta 36.5 ±0
  3. #346 Codex Bridge 36.5 this agent
  4. #347 Pordee 36.3 −0.2
  5. #348 Iothackbot 34.9 −1.6

Bars show each HVTrust score; the tick marks Codex Bridge’s 36.5.

Where the 36.5 comes from

HVTrust dimensions vs the Agent Skills average

36.5 / 100 · 100.0% confidence

Codex Bridge Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.2 / 25
4.6 below avg 7.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
10.7 / 17
1.4 below avg 12.1
Maintenance60% last-push freshness · 40% commit activity
7.9 / 20
6.2 below avg 14.1
AdoptionLog-scaled stars · package downloads
5.7 / 20
3.3 below avg 9.0

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-25
Rank Moved
Rank dropped 23 spots (#310 → #333)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.6/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 62 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Codex Bridge View Agent Skills Report missing data
35.1
Activity sub-score · out of 100
#346
In Agent Skills

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-11 04:08 UTC · Repo last pushed 62 days ago

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
246
Forks
7
Last Push
2026-08-10
62 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
▼2
was #344

Analysis

Activity Inputs

35.1 / 100
StarsRepository reach
14.4 / 30
FreshnessLast push recency
16.4 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
4.2 / 20

Common questions about Codex Bridge

Public trust evidence for Codex Bridge is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Codex Bridge publish package provenance?
No published build provenance is currently detected for Codex Bridge. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Codex Bridge have an OpenSSF Scorecard?
Codex Bridge has an OpenSSF Scorecard score of 2.6/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Codex Bridge actively maintained?
Slowing down. Last push was 62 days ago — keep an eye on whether activity resumes.
What license does Codex Bridge use?
Codex Bridge ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Codex Bridge's commits signed?
0% of the last 100 commits to Codex Bridge are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Codex Bridge's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI

Maintain Codex Bridge?

For maintainers

HVTrust scores Codex Bridge from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 11Listed 2HVTrust 2Score 2Scorecard 1Delisted 1Surface 1Surface 1
2026-09-25
Rank Moved
Rank dropped 23 spots (#310 → #333)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI
2026-09-23
Rank Moved
Rank dropped 47 spots (#263 → #310)
2026-09-23
HVTrust Changed
HVTrust up 6.7pts (31.1 → 37.8)
2026-09-22
Newly Listed
First tracked at rank #263
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-11
Rank Moved
Rank dropped 11 spots (#287 → #298)
2026-09-09
Rank Moved
Rank dropped 16 spots (#262 → #278)
2026-09-09
Activity Score Changed
Activity score down 6pts (44 → 38)
2026-09-08
Rank Moved
Rank dropped 17 spots (#245 → #262)
2026-09-08
Activity Score Changed
Activity score down 6pts (50 → 44)
2026-09-03
Rank Moved
Rank dropped 10 spots (#205 → #215)
2026-09-02
Rank Moved
Rank dropped 12 spots (#193 → #205)
2026-09-01
Rank Moved
Rank dropped 15 spots (#178 → #193)
2026-08-31
Rank Moved
Rank dropped 18 spots (#160 → #178)
2026-08-30
Scorecard Added
OSSF Scorecard: 2.6/10
2026-08-30
Rank Moved
Rank rose 131 spots (#291 → #160)
2026-08-30
HVTrust Changed
HVTrust up 25.2pts (18.0 → 43.2)
2026-08-29
Rank Moved
Rank dropped 10 spots (#281 → #291)
2026-08-26
Newly Listed
First tracked at rank #269
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 36.5 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/codex-bridge.svg)](https://hvtracker.net/agents/codex-bridge)
HTML:
<a href="https://hvtracker.net/agents/codex-bridge"><img src="https://hvtracker.net/badge/codex-bridge.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON