Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers exploring whether an agent-native desktop IDE can be more productive than bolting chat onto a conventional editor.
Who should use it
Who should skip it
Avoid running evanklem/polypore in production until you have reviewed its permissions, data-access scope, and failure modes in a sandbox.
About this signal
evanklem/polypore is tracked by RepoRadar as a app in the AI Coding section. It was first seen on 2026-06-26 and last updated on 2026-06-26. The current verdict is 'worth watch' with a Gold tier and moderate setup difficulty. evanklem/polypore leads on open-source/build quality (8.4) and workflow potential (8.4); its lowest signal is momentum (6.0), so factor that in before investing setup time. 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 evanklem/polypore 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 75.0 and never affects the composite score or tier. The risk label of 'medium' 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 evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
The workspace centralizes code access, agent actions, MCP connections, and secrets handling, so the blast radius is wider than a plain editor if it is misconfigured; The project is still at v0.1.0, which means workflows, persistence, and integration boundaries may shift quickly as the product settles; Early agent IDEs can feel compelling in demos while still missing edge-case polish on large or sensitive repos, so trial it before standardizing on it.