Email: [email protected]
This link opens your email application. The website has no contact form, ticket submission or file upload.
Make a correction easy to check
For a content correction, include the page URL, the sentence or section in question, and a primary source that supports the change. If the issue depends on a product release, add the relevant version and documentation date.
For a checker issue, include your browser, the selected language, the rule ID or visible error, and the result you expected. A short synthetic example is more useful than a complete repository. Explain whether it is a false positive, a missing diagnostic, an incorrect location or a loading problem.
Keep private code out of email
The checker processes snippets locally. Email is a separate service: anything you send becomes part of a message handled by your email provider and the services used to receive it. Do not include API keys, access tokens, customer records, sensitive personal data or code you are not permitted to share.
Replace private identifiers and values with synthetic ones before sending a reproducer. For a security concern, begin with a brief description and a way to contact you rather than sending working credentials or private data.
What this channel covers
This address is for the AI Code Verify project and its published material. It is not an emergency service, a confidential code-review contract or a promise of a response within a specific period. A message does not by itself create a support engagement or authorize access to a repository.
For details about code processing, optional analytics and email handling, read the privacy notice. For the tool’s practical limits, see the published scope and rule list.