Is Codex safe to use?

Codex has an HVTrust score of 93.8/100 (Grade A), ranked #3 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Codex?

Codex scores 93.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 105.3k GitHub stars and is categorized under Coding Agents.

Codex

openai/codex

Lightweight coding agent that runs in your terminal

Coding Agents Rust Grade A Listed Apache-2.0

93.8/100

Rank #3 of 1283

Compare Codex

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-11 · 0d ago

Recent change

No recent signal change

Is Codex safe? Codex scores 93.8/100 (Grade A), ranked #3 of 1283 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.0/10; 100% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#2 Cline — 91.3 (A) → #3 Qwen Code — 90.9 (A) → #4 ECC — 88.1 (A) → #5 Hermes Agent — 86.8 (A) →

Quick Trust Read

What Would Improve It

Improve transparency to lift the weakest part of the trust profile.

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.0/10. Tighten the weakest checks to improve public safety evidence.

Compare with Cline Get email alerts for Codex View Coding Agents Report missing data

99.5

Activity sub-score · out of 100

In Coding Agents

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

Activity & Reach

Stars

105.3k

Forks

16.0k

Last Push

2026-08-11

today

Commits (4 wk)

1002

Downloads (7d)

10,929,573

npm+pypi

HN mentions (30d)

—

Open Issues

12094

Rank Change

was #3

Analysis

HVTrust Dimensions vs Coding Agents

93.8 / 100 · 100.0% confidence

Codex Coding Agents average (67 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

20.0 / 25

12.3 above avg 7.7

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

6.3 above avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

13.6 / 17

2.5 above avg 11.1

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

4.7 above avg 15.3

AdoptionLog-scaled stars · package downloads

20.0 / 20

7.8 above avg 12.2

Activity Inputs

99.5 / 100

StarsRepository reach

30 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

19.5 / 20

Supply Chain Trust

Package Provenance

Verified

npm, pypi attestation

OSSF Scorecard

6.0 / 10

OpenSSF Scorecard · scanned Aug 11, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 4

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 8

SAST 0

Security-Policy 10

Signed-Releases 8

Token-Permissions 0

Vulnerabilities 0

Is Codex safe?

Public supply-chain signals for Codex are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Codex carries less obvious unverified-evidence risk than projects with thin signals.

Does Codex publish package provenance?

Yes. Codex's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Codex have an OpenSSF Scorecard?

Codex has an OpenSSF Scorecard score of 6.0/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 actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Codex use?

Codex ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Codex's commits signed?

100% of the last 100 commits to Codex 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.

Compare Codex head-to-head

Codex vs Cline → Codex vs Qwen Code → Codex vs ECC →

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

high confidence

Implemented

Codex appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

OpenAI

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

medium confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

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'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-05-30

Provenance Added

Package provenance attestation detected

Maintain Codex?

For maintainers

HVTrust scores Codex 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

2026-05-30

Provenance Added

Package provenance attestation detected

2026-05-30

Grade Changed

Trust grade D → C

2026-05-30

Rank Moved

Rank rose 35 spots (#37 → #2)

2026-05-30

HVTrust Changed

HVTrust up 21.1pts (70.4 → 91.5)

2026-05-29

HVTrust Changed

HVTrust up 10.0pts (60.4 → 70.4)

2026-05-28

Activity Score Changed

Activity score up 25pts (74 → 99)

2026-05-25

Rank Moved

Rank dropped 14 spots (#8 → #22)

2026-05-24

Newly Listed

First tracked at rank #8

GitHub → PyPI: openai-codex npm: @openai/codex

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/codex.svg)](https://hvtracker.net/agents/codex)
            
HTML:
            <a href="https://hvtracker.net/agents/codex"><img src="https://hvtracker.net/badge/codex.svg" alt="HVTrust"></a>

Other agents in Coding Agents

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON