Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that want a practical coding agent with explicit approval and audit paths before they trust it in security-sensitive or compliance-heavy repos.
Who should use it
Who should skip it
Skip arthurpanhku/dvalincode if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
arthurpanhku/dvalincode is tracked by RepoRadar as a agent in the Coding Agents 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. Across RepoRadar's eight signals, arthurpanhku/dvalincode is strongest on workflow potential (9.5) and open-source/build quality (8.4) and weakest on maturity (6.3) — a profile worth weighing against your own priorities. 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 arthurpanhku/dvalincode 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
Its autonomous code mode can execute shell tooling and write files, so initial rollout should stay in a sandboxed repo or disposable worktree with least-privileged credentials; Approval and audit features help, but they do not replace normal code review or secret-handling controls in sensitive repositories.