1jehuang/jcode
High performance coding agent harness written in rust
20.8k stars · 2.4k forks · Rust
Caution
Caution: one person wrote most of the recent commits.
Why
- One person wrote 81% of human commits in the last year, so the project depends on them continuing. (source 1, source 2)
What would change this
- A second person takes a substantial share of commits.
- Partly checked: maintenance (Commit counts are estimated: the commit sample stops before the window start, so GitHub's totals were scaled by the sampled bot share.; Authors in the last 90 days are counted from the sampled commits only.)
Maintenance
PartialActive
- Human commits, 30 days
- 938
- Human commits, 90 days
- 4.5k
- Human commits, 365 days
- 10k
- Bot share of commits, 365 days
- 3%
- Last commit
- Oct 14, 2026 (9 hours ago)
- Last human commit
- Oct 14, 2026 (9 hours ago)
- Authors, 90 days
- 24
- Last release
- Oct 14, 2026 (17 hours ago)
- Median PR merge time
- 19 hours
Responsiveness: of 29 recent issues, 100% got a maintainer reply. Median first response: 31 hours.
- Commit counts are estimated: the commit sample stops before the window start, so GitHub's totals were scaled by the sampled bot share.
- Authors in the last 90 days are counted from the sampled commits only.
Sources: Commits, Releases, Merged pull requests, Issues
People
Complete- Owner
- Personal account
- Commits sampled
- 486 since Oct 14, 2025
- Authors for half of commits
- 1
- Authors for 80% of commits
- 1
- Contributors
- 44
Top committers
- 1jehuang: 81% of commits
- SiavZ: 6% of commits
- gdamprint-cmyk: 3% of commits
- mg-mg-mg: 1% of commits
- Soham-o: 1% of commits
- Shares come from the newest sampled commits, since the commit sample is capped.
Sources: Commits, Contributors
Stars
CompleteOrganic, confidence high
Bursts
- Feb 21, 2026 to Feb 25, 2026: about 45 more stars than usual, peak 23 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Mar 4, 2026 to Mar 5, 2026: about 33 more stars than usual, peak 21 in one day, a spike that tapers off. Outside explanation: a jump in issues and pull requests.
- Mar 29, 2026 to Apr 4, 2026: about 123 more stars than usual, peak 44 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Apr 27, 2026 to May 29, 2026: about 6.1k more stars than usual, peak 593 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Jun 20, 2026 to Jun 24, 2026: about 341 more stars than usual, peak 165 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Jun 29, 2026 to Jul 1, 2026: about 139 more stars than usual, peak 91 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Jul 18, 2026 to Aug 19, 2026: about 8.7k more stars than usual, peak 759 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Oct 11, 2026 to Oct 13, 2026: about 239 more stars than usual, peak 137 in one day, a shape we can't classify. Outside explanation: a jump in forks, a jump in issues and pull requests.
- 4 stars GitHub has since removed (tracked since Oct 14, 2026).
Anyone can buy stars for any repo; bursts alone don't prove the owner did.
- The star history looks organic.
Sources: How star history is analyzed
Risk
CompleteFlags
No risk flags.
License
- Now
- MIT (OSI-approved)
- A year ago
- Not known
Packages
No published packages found.
Sources: GitHub: 1jehuang/jcode
Badge
Add this to a README to show the current verdict:
[](https://reporadar.ai/1jehuang/jcode)Earlier verdicts
- Oct 14, 2026: Caution
- Oct 14, 2026: Caution
Computed 8 hours ago · method 2026.10.2