Corrections policy
Effective 2026-10-07
If a result is wrong, please tell us. What It Calls shows only facts found in code, so fixing wrong results quickly matters most.
How to report
Click “This result is wrong” on a result page to open the correction form.
- Wrong items — mark what you think is wrong: the repository state, a row of the external API table, a tag and so on.
- Description — explain what is wrong and why.
- Contact email (optional) — only if you want a reply. It is stored encrypted and used only to reply. See the privacy policy.
We accept up to 5 correction requests per IP per day.
Point to the evidence line
A result does not decide whether an external API is needed; it links to where the code calls it. So instead of “this isn’t needed”, the fastest reports point to the evidence line, for example:
- The linked line is not actually a call (a log string, a comment, a test and so on)
- The call is made only by a maintenance script
- The code has a setting to switch to local that the result missed (tell us the file and line)
- The provider’s pricing has changed (send the official pricing page link)
Review and action
The operator reviews each request personally, aiming to finish within 72 hours. After review, one of these actions is taken:
| Action | What happens |
|---|---|
| Fix the result | The verdict rules or pricing catalog are corrected, the repository is checked again and a new revision is published. Other results with the same cause change too. |
| Take the result down | The result is made private. |
| No change | The code evidence was rechecked and the result holds. The reason is recorded in the history. |
We do not hand-edit a single repository’s result. Fixes go into the rules or the catalog so that the same rules apply to every repository.
Public correction history
Actions are listed on that result page under “Correction history” with the date, item and action. Personal information such as the reporter’s email is never shown.
For repository maintainers
Requests from repository maintainers are welcome. You know the code best, and pointing to the evidence line helps us fix the rules. If you have pushed new commits, use “Check the latest commit” on the result page to check again right away.
Urgent cases
If a quote on a result page exposes personal information or a secret (such as an API key), skip the form and email siwooeo@gmail.com directly with the result page address. We handle these first.