Corrections
Report an error
RepoRadar should correct material errors quickly and visibly. Use this guided page to report broken links, incorrect descriptions, score concerns, evidence gaps, or risk-label mistakes.
Fastest correction path
Email admin [at] reporadar [dot] ai with the item URL and the evidence that supports the correction. Plain email is preferred because it preserves links, screenshots, and context without asking you to create an account.
Use this template
- RepoRadar page: paste the /item/ URL or source title.
- What is wrong: broken source link, description error, score concern, risk-label issue, outdated status, or missing disclosure.
- What should change: the corrected wording, URL, label, or evidence level.
- Evidence: official docs, changelog, README, model card, paper, release note, or package page.
- Disclosure: say if you are the founder, employee, investor, sponsor, or affiliate of the project.
Expected turnaround: obvious broken links and factual mistakes are prioritized. Score or risk-label disputes are reviewed against the methodology and may take longer because they require source checks.
Examples of useful reports
- “The GitHub link for this item now 404s; the project moved to this official repo.”
- “The description says local-only, but the docs show it sends prompts to a hosted API by default.”
- “This item is marked high risk, but the linked release is read-only and does not request file, shell, OAuth, or account access.”
- “The project changed license from MIT to source-available on this date; the open-source note should be updated.”
Correction policy
Corrections are evidence-first. RepoRadar updates facts, source links, descriptions, risk labels, and caution notes when primary evidence supports the change. Vendor and founder submissions are welcome, but they are treated as unverified until evidence is checked. Paid support never changes the outcome.