updated 2026-08-19 05:02 UTC

jcode

1jehuang/jcode

The most RAM efficient harness

Coding Agents Rust Grade D Listed MIT
22.3/100
Rank #973 of 1308
Compare jcode

How does it stack up against its Coding Agents 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 D · 1/5 signals
Last push
2026-08-19 · 0d ago
Recent change
Rank +3

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

Ranked neighbours in Coding Agents

#64 loushang — 23.1 (D) → #65 Plandex — 22.5 (D) → #67 SWE-AF — 21.1 (D) → #68 Kodu — 19.6 (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-17
Rank Moved
Rank rose 14 spots (#979 → #965)
2026-08-16
Rank Moved
Rank dropped 26 spots (#953 → #979)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none
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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for jcode View Coding Agents Report missing data
90.9
Activity sub-score · out of 100
#66
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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-19 05:02 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars
18.0k
Forks
2.0k
Last Push
2026-08-19
today
Commits (4 wk)
1289
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
326
Rank Change
▼5
was #968

Analysis

HVTrust Dimensions vs Coding Agents

22.3 / 100 · 50.0% confidence

jcode Coding Agents average (70 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0.1 / 25
7.4 below avg 7.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
2.6 below avg 11.1
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
4.7 above avg 15.3
AdoptionLog-scaled stars · package downloads
10.2 / 20
2.1 below avg 12.3

Activity Inputs

90.9 / 100
StarsRepository reach
25.5 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
1%
of last 100 commits verified

Is jcode safe?

Public trust evidence for jcode 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 jcode publish package provenance?
No published build provenance is currently detected for jcode. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does jcode have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for jcode. 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 jcode actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does jcode use?
jcode ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are jcode's commits signed?
1% of the last 100 commits to jcode 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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
4 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
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
How this surface has changed

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.

2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 5Listed 1Surface 1
2026-08-17
Rank Moved
Rank rose 14 spots (#979 → #965)
2026-08-16
Rank Moved
Rank dropped 26 spots (#953 → #979)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none
2026-08-12
Rank Moved
Rank rose 38 spots (#985 → #947)
2026-08-10
Rank Moved
Rank dropped 59 spots (#923 → #982)
2026-08-08
Rank Moved
Rank dropped 408 spots (#474 → #882)
2026-08-06
Newly Listed
First tracked at rank #451
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in Coding Agents

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