Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that want a coding-agent CLI with explicit verification constraints, real npm-install distribution, and a benchmark record they can audit instead of another thin wrapper around one provider.
Who should use it
Who should skip it
Skip linghungegeg/Linghun if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
linghungegeg/Linghun is tracked by RepoRadar as a developer tool in the Coding Agent / CLI section. It was first seen on 2026-07-01 and last updated on 2026-07-01. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for linghungegeg/Linghun are workflow potential (9.5) and open-source/build quality (8.4), while momentum (6.0) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned linghungegeg/Linghun a composite score of 8.0 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
It runs in your shell and can edit files, so first evaluation should stay on a disposable project with no secrets or production data; The package is still at 0.1.x with rapid 0.1.0-0.1.8 release cadence, so verify API stability before wiring it into a team workflow.