Is CodeGraphContext safe to use?

CodeGraphContext has an HVTrust score of 43.2/100 (Grade D), ranked #563 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for CodeGraphContext?

CodeGraphContext scores 43.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 4.1k GitHub stars and is categorized under Memory & Knowledge.

CodeGraphContext

CodeGraphContext/CodeGraphContext

An MCP server plus a CLI tool that indexes local code into a graph database to provide context to AI assistants.

Memory & Knowledge Python Grade D Listed MIT

43.2/100

Rank #563 of 1283

Compare CodeGraphContext

How does it stack up against its Memory & Knowledge neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-08 · 4d ago

Recent change

New

Is CodeGraphContext safe? CodeGraphContext scores 43.2/100 (Grade D), ranked #563 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 97% of recent commits are signed; last pushed 2026-08-08. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#35 ByteRover CLI — 47.1 (D) → #36 EverOS — 46.7 (D) → #38 AnythingLLM — 43.1 (D) → #39 Pond — 37.5 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-10

Newly Listed

First tracked at rank #562

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for CodeGraphContext View Memory & Knowledge Report missing data

84.8

Activity sub-score · out of 100

#37

In Memory & Knowledge

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 →

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars

4.1k

Forks

807

Last Push

2026-08-08

4 days ago

Commits (4 wk)

157

Downloads (7d)

4,452

pypi

HN mentions (30d)

—

Open Issues

118

Rank Change

▲2

was #565

Analysis

HVTrust Dimensions vs Memory & Knowledge

43.2 / 100 · 67.0% confidence

CodeGraphContext Memory & Knowledge average (42 agents)

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

4.9 / 25

5.2 below avg 10.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.4 below avg 12.2

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

4.0 below avg 12.5

Maintenance60% last-push freshness · 40% commit activity

19.7 / 20

2.0 above avg 17.7

AdoptionLog-scaled stars · package downloads

13.5 / 20

in line with avg 13.6

Activity Inputs

84.8 / 100

StarsRepository reach

21.7 / 30

FreshnessLast push recency

24.4 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

13.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

97%

of last 100 commits verified

Is CodeGraphContext safe?

Public trust evidence for CodeGraphContext 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 CodeGraphContext publish package provenance?

No published build provenance is currently detected for CodeGraphContext. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does CodeGraphContext have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for CodeGraphContext. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is CodeGraphContext actively maintained?

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

What license does CodeGraphContext use?

CodeGraphContext ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are CodeGraphContext's commits signed?

97% of the last 100 commits to CodeGraphContext 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

CodeGraphContext appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

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

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

database

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

Maintain CodeGraphContext?

For maintainers

HVTrust scores CodeGraphContext 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-08-10

Newly Listed

First tracked at rank #562

GitHub → PyPI: codegraphcontext

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Memory & Knowledge

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