Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers who want a repo search layer that is optimized for coding-agent token efficiency rather than for humans reading raw grep output.
Who should use it
Who should skip it
Pass on hunhee98/pluck if its scope or audience does not match what your team is building right now.
About this signal
hunhee98/pluck is tracked by RepoRadar as a code retrieval in the Developer Tools section. It was first seen on 2026-06-28 and last updated on 2026-06-28. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for hunhee98/pluck are workflow potential (9.7) 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 hunhee98/pluck a composite score of 8.2 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 evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
Its install and init flow can add project-level agent config and retrieval policy files, so review the generated setup before applying it to a shared repository; The README's token-savings figures come from the maintainer's own benchmarks, so validate the gains on your own codebase before standardizing on it.