Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that want agents to work against documentation without giving up inspectability: convert one internal or third-party docs set, then see whether OKF bundles are easier to diff, version, and debug than your current doc-retrieval path.
Where this stands now
0dust/OKFy ranks #602 of 3231 tracked Radar items by composite score (7.9 against a section median of 4.9). The section currently carries 2115 Bronze, 645 Gold, 471 Silver. RepoRadar has retained observations for this record since 2026-06-19 (113 days in the current window). Signal extremes versus the section: novelty at the 72th percentile.
Who should use it
Who should skip it
Skip 0dust/OKFy if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
0dust/OKFy is tracked by RepoRadar as a developer tool in the Radar section. First seen 2026-06-19; the source record was last checked on 2026-06-19. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. Across RepoRadar's eight signals, 0dust/OKFy is strongest on workflow potential (9.0) and open-source/build quality (8.4) and weakest on momentum (5.0) — a profile worth weighing against your own priorities. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The 0dust/OKFy record combines a 7.9/10 composite score with separate popularity (31.0), risk (none), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Questions worth asking before you adopt this
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
No inherent user-impacting risk is flagged from the captured evidence.