jcode
Website
High performance coding agent harness written in Rust, built for heavy multi-agent dev workflows
Is jcode safe? Promising trust profile, but some evidence still deserves review.
Compare jcode
How does it stack up against its Coding Agents neighbours?
Pick any agent to compare →In detail: jcode scores 57.7/100 (Grade C), ranked #773 of 1374 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 3.8/10; recent commits are unsigned; last pushed 2026-11-05. Every point is earned from checkable signals — never paid placement. How scoring works →
How jcode 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.
- Raise the OSSF Scorecard from 3.8 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +10.8 → 68.5 B · #20 of 77
- Sign every commit0% signed today +5.0 → 62.7 C · #33 of 77
Chain of custody
Scanners check what the code says. This traces who ships jcode 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.
-
Source Unsigned
github.com/1jehuang/jcode, MIT, last pushed 2026-11-05. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.
-
Review and release Weak
OpenSSF Scorecard rates the repository's practices 3.8/10 (scanned Oct 30, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 0CI-Tests -1CII-Best-Practices 0Code-Review 0Contributors 6Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 0SAST 0Security-Policy 0Signed-Releases 0Token-Permissions 0Vulnerabilities 6 -
Published packages None
No registry package. jcode 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-09-03 OSSF Scorecard: 3.8/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 jcode’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.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How jcode compares in Coding Agents
- #47 MonkeyCode 57.9 +0.2
- #48 Vercel fx 57.8 +0.1
- #49 jcode 57.7 this agent
- #50 Vibe Kanban 56.7 −1.0
- #51 freebuff 56.3 −1.4
Bars show each HVTrust score; the tick marks jcode’s 57.7.
Where the 57.7 comes from
HVTrust dimensions vs the Coding Agents average
57.7 / 100 · 100.0% confidencejcode Coding Agents average (77 agents)
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
91.8 / 100Common questions about jcode
Does jcode publish package provenance?
Does jcode have an OpenSSF Scorecard?
Is jcode actively maintained?
What license does jcode use?
Are jcode's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to jcode'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.
Maintain jcode?
For maintainers
HVTrust scores jcode 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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/jcode)
<a href="https://hvtracker.net/agents/jcode"><img src="https://hvtracker.net/badge/jcode.svg" alt="HVTrust"></a>
Other agents in Coding Agents
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