Is jcode safe to use?

jcode has an HVTrust score of 57.5/100 (Grade C), ranked #688 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for jcode?

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

jcode

1jehuang/jcode

The most RAM efficient harness

Coding Agents Rust Grade C Listed MIT

57.5/100

Rank #688 of 1328

Compare jcode

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

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-09-20 · 0d ago

Recent change

Rank +1

Is jcode safe? jcode scores 57.5/100 (Grade C), ranked #688 of 1328 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.9/10; 5% of recent commits are signed; last pushed 2026-09-20. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#40 MonkeyCode — 58.2 (C) → #41 Vercel fx — 57.6 (C) → #43 Vibe Kanban — 56.9 (C) → #44 loushang — 56.8 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-19

Rank Moved

Rank rose 14 spots (#703 → #689)

2026-09-16

Rank Moved

Rank rose 17 spots (#712 → #695)

2026-09-07

Rank Moved

Rank dropped 39 spots (#643 → #682)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.9/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.

Compare with another agent Get email alerts for jcode View Coding Agents Report missing data

91.4

Activity sub-score · out of 100

#42

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 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

2026-08-11 2026-09-20

Activity & Reach

Stars

19.9k

Forks

2.3k

Last Push

2026-09-20

today

Commits (4 wk)

797

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

469

Rank Change

▲1

was #689

Analysis

HVTrust Dimensions vs Coding Agents

57.5 / 100 · 100.0% confidence

jcode Coding Agents average (72 agents)

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

5.1 / 25

3.9 below avg 9.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.0 below avg 11.8

Transparency50% declared license · 50% OSSF Scorecard

11.8 / 17

in line with avg 11.8

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

5.2 above avg 14.8

AdoptionLog-scaled stars · package downloads

10.3 / 20

1.9 below avg 12.2

Activity Inputs

91.4 / 100

StarsRepository reach

25.8 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

15.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.9 / 10

OpenSSF Scorecard · scanned Sep 19, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 9

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 6

Is jcode safe?

jcode 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 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?

jcode has an OpenSSF Scorecard score of 3.9/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 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?

5% 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

high confidence

Implemented

jcode appears to expose MCP server capabilities.

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-09-06

Mcp Status Changed

Detected MCP server support changed: declared → implemented

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

2026-09-19

Rank Moved

Rank rose 14 spots (#703 → #689)

2026-09-16

Rank Moved

Rank rose 17 spots (#712 → #695)

2026-09-07

Rank Moved

Rank dropped 39 spots (#643 → #682)

2026-09-06

Mcp Status Changed

Detected MCP server support changed: declared → implemented

2026-09-06

Rank Moved

Rank rose 41 spots (#684 → #643)

2026-09-05

Rank Moved

Rank dropped 86 spots (#598 → #684)

2026-09-04

Rank Moved

Rank dropped 15 spots (#583 → #598)

2026-09-03

Scorecard Added

OSSF Scorecard: 3.8/10

2026-09-03

Grade Changed

Trust grade D → C

2026-09-03

Rank Moved

Rank rose 665 spots (#1248 → #583)

2026-09-03

HVTrust Changed

HVTrust up 33.1pts (22.4 → 55.5)

2026-09-02

Rank Moved

Rank dropped 30 spots (#1218 → #1248)

2026-09-01

Rank Moved

Rank dropped 28 spots (#1190 → #1218)

2026-08-31

Rank Moved

Rank dropped 31 spots (#1159 → #1190)

2026-08-30

Rank Moved

Rank dropped 36 spots (#1123 → #1159)

2026-08-29

Rank Moved

Rank dropped 36 spots (#1087 → #1123)

2026-08-28

Rank Moved

Rank dropped 29 spots (#1058 → #1087)

2026-08-27

Rank Moved

Rank dropped 14 spots (#1044 → #1058)

2026-08-26

Rank Moved

Rank dropped 81 spots (#963 → #1044)

2026-08-24

Rank Moved

Rank dropped 11 spots (#954 → #965)

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

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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON