CodeGraph

Pre-indexed code knowledge graph, auto syncs on code changes, for Claude Code, Codex, Gemini, Cursor, OpenCode, AntiGrav

Protocols & Tool Integration C Grade C Listed MIT
59.8/100
Rank #463 of 1320
Compare CodeGraph

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-31 · 4d ago
Recent change
Rank +9

Is CodeGraph safe? CodeGraph scores 59.8/100 (Grade C), ranked #463 of 1320 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.7/10; 30% of recent commits are signed; last pushed 2026-08-31. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 24 spots (#439 → #463)
2026-09-03
Rank Moved
Rank dropped 24 spots (#415 → #439)
2026-09-02
Rank Moved
Rank dropped 10 spots (#405 → #415)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.7/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.
95.7
Activity sub-score · out of 100
#33

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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-09-04 22:32 UTC · Repo last pushed 4 days ago

Rank Trend

2026-08-27 2026-09-04

Activity & Reach

Stars
69.6k
Forks
4.4k
Last Push
2026-08-31
4 days ago
Commits (4 wk)
137
Downloads (7d)
HN mentions (30d)
Open Issues
174
Rank Change
▼24
was #439

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

59.8 / 100 · 100.0% confidence

CodeGraph Protocols & Tool Integration average (61 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.9 / 25
5.5 below avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
10.8 / 17
1.9 below avg 12.7
Maintenance60% last-push freshness · 40% commit activity
19.7 / 20
5.4 above avg 14.3
AdoptionLog-scaled stars · package downloads
11.6 / 20
1.6 above avg 10.0

Activity Inputs

95.7 / 100
StarsRepository reach
29.1 / 30
FreshnessLast push recency
24.4 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
17.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
2.7 / 10
OpenSSF Scorecard · scanned Sep 4, 2026
Signed Commits
30%
of last 100 commits verified
Binary-Artifacts 0
Branch-Protection 5
CI-Tests 0
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 2
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Is CodeGraph safe?

CodeGraph has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does CodeGraph publish package provenance?
No published build provenance is currently detected for CodeGraph. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does CodeGraph have an OpenSSF Scorecard?
CodeGraph has an OpenSSF Scorecard score of 2.7/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 CodeGraph actively maintained?
Actively maintained. The repository was pushed to within the last 4 day(s).
What license does CodeGraph use?
CodeGraph ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are CodeGraph's commits signed?
30% of the last 100 commits to CodeGraph 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
high confidence
Implemented
CodeGraph appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool 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

Maintain CodeGraph?

For maintainers

HVTrust scores CodeGraph 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.

Reputation Timeline

Signal history
Rank 7Listed 1HVTrust 1Grade 1Scorecard 1
2026-09-04
Rank Moved
Rank dropped 24 spots (#439 → #463)
2026-09-03
Rank Moved
Rank dropped 24 spots (#415 → #439)
2026-09-02
Rank Moved
Rank dropped 10 spots (#405 → #415)
2026-09-01
Rank Moved
Rank dropped 10 spots (#395 → #405)
2026-08-31
Rank Moved
Rank dropped 24 spots (#371 → #395)
2026-08-29
Scorecard Added
OSSF Scorecard: 3.0/10
2026-08-29
Grade Changed
Trust grade D → C
2026-08-29
Rank Moved
Rank rose 596 spots (#974 → #378)
2026-08-29
HVTrust Changed
HVTrust up 32.3pts (28.1 → 60.4)
2026-08-28
Rank Moved
Rank dropped 36 spots (#938 → #974)
2026-08-27
Newly Listed
First tracked at rank #938

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 59.8 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/codegraph.svg)](https://hvtracker.net/agents/codegraph)
HTML:
<a href="https://hvtracker.net/agents/codegraph"><img src="https://hvtracker.net/badge/codegraph.svg" alt="HVTrust"></a>

Other agents in Protocols & Tool Integration

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.3 · Raw JSON