Skip to report

Independent analytics for a public GitHub repository

1jehuang/jcode

The most RAM efficient harness — view on GitHub · jcode.sh

Language

Rust

License

MIT

open source

Created

Jan 2026

Stars

19,975

Forks

2,320

Issues

477 open

Updated 21 Sept 2026, 17:58 UTC

86 /100
ACTIVELY MAINTAINED

tracker score 86/100 methodology →

Computed from release cadence, responsiveness, backlog trend and contributor depth.

Last release

1 days ago

v0.86.0

Cadence

bursty, <1d median

on pace

PR merge median

0.7d

Issue response median

31.0h

Commits / 7d

136

Attention vs delivery — is popularity translating into shipping?

The signature question of dependency due diligence. Columns: commits per month (activity). Line: merged pull requests per month (delivery). 12 full months.

attention — commits / month delivery — merged PRs / month stable release

Reading: delivery held at ~5 merged PRs/mo over the last 12 months. No divergence risk — delivery tracks attention.

Responsiveness — vs cohort percentiles

How fast maintainers answer, review and merge — ranked against repos of similar size and age.

Issue first non-author response

median 31.0hcohort: n/a

PR first review

median 0.3hcohort: n/a

PR merge time

median 0.7dcohort: n/a

Bots excluded Sample: 106 merged PRs (90d) / 58 recent issues. Percentile position measured from the left — shorter is faster.

First-contributor funnel — what happens to a newcomer’s PR?

25

first-time PRs (12 mo)

80%

got a response

n=91 scanned

0%

were merged

81 newcomer candidates

28%

returned ≤90d

verified via author history

Verdict: tough room for newcomers — only 80% of verified first-time PRs got a maintainer-class response and 0% merged (window 2026-03-25..2026-06-23). The core team ships fast, but drive-by PRs mostly sit open.

Contributor concentration (12 mo)

top 1 — 99.6% of accepted changes · last commit Sep 20

top 3 — 99.8% of accepted changes

long tail — 9 further authors

Verdict: high key-person risk. 12 human commit authors in 12 months; top author (1jehuang) holds 99.6%, top 3 hold 99.8%, 1 authors above 1% each.

Open-issue backlog

Open issues and pull requests right now. Trend history builds from daily tracking.

open issues & PRs — right now

477

open issues

41

open pull requests

Tracking daily since 25 Aug 2026 — 25 snapshots so far. Score moved 76 → 86 over the past 27d.

518 open

477 issues + 41 PRs · backlog up 48% over 27d

Fork network & successors

2,320 forks · 0 with independent momentum

quangdang46/jcode — 3★ · last push 67d ago

alive

1jehuang/jcode is upstream — no successor needed (project active). Top forks by stars are all stale (pushes >1y ago). Successor detection activates if the repo goes dormant.

If this repo goes dormant, this section becomes “Where did development continue?” — with evidence labels per fork.

What changed — last 90d

74 stable releases in 90d (median gap 0.8d)

Issue response sits at a 31.0h median — down from 80.3h 27d ago

License unchanged · not archived · no rename/transfer

Max release gap in 12mo: 12d (cadence 0.8d median)

Frequently asked answered from live data · FAQPage structured data

These answers regenerate on every snapshot — they never rot.

Is jcode still maintained?

Yes — actively (score 86/100). Last stable release v0.86.0 1 days ago, 136 commits in the last full week, median PR merge 0.7d. Evidence collected Mon Sep 21 2026.

What license does jcode use?

MIT — as reported by GitHub.

When was the last jcode release?

v0.86.0, 1 days ago. Median gap between stable releases is 0.8 days; 74 stable releases shipped in the last 90 days.

Is jcode safe to adopt for a new project in 2026?

On the evidence: yes. 12 human authors in 12 months, no fork-succession pressure. Caveat for contributors: the newcomer funnel is weak (0% first-PR merge rate). Not published to npm — GitHub activity only.

Share & embed — every share is a branded mini-report

Link preview (auto-generated OG card)

tracker.git.tools

1jehuang/jcode

ACTIVELY MAINTAINED · 86/100

ships bursty, <1d median · PR merge 0.7d · ★ 19,975

1jehuang/jcode — maintenance verdict & repo intelligence · tracker.git.tools

README badge (live SVG — every embed is a backlink)

maintenance active · 86
[![maintenance](https://tracker.git.tools/badge/1jehuang/jcode)](https://tracker.git.tools/1jehuang/jcode)

Badge states: active · slowing · maintenance-only · dormant — flips automatically; maintainers embed it because it’s honest.

Methodology

Built from the public GitHub API, the npm registry, deps.dev and Hacker News. Known bot accounts are excluded from response and merge metrics. Verdicts are computed from the evidence shown on this page — nothing is scored that you cannot see. Reports refresh daily.