Represent a project or correct the record.
Project representatives can request verification. Any reader can report an error without representing the project. Both routes remain subject to review.
Representing a project
Select Represent this project on the relevant Directory profile and sign in. The available verification route follows the official URL recorded for that project.
Projects with their own domain
For a project-owned website, the verification page offers a small HTML verification file or a homepage meta tag. OpenViST checks the exact listed website. Where offered, a published work-email route requests manual review rather than automatic verification. Never send passwords or unnecessary identity documents.
Projects listed through GitHub
Place the unique verification file in the default branch of the exact public repository shown on the profile. OpenViST checks that file through the public GitHub API. A fork, issue, another repository or an unmerged pull request does not satisfy this check. No GitHub password or access token is requested.
Other hosted platforms
Projects listed through a shared hosting domain, package registry or application store use manual evidence review. Provide your role and a relevant public source through the offered contact route. Control of the shared platform domain is not requested.
What verification establishes
A successful technical check records control of the listed website or access to the exact repository. It does not establish legal ownership or authority to speak for an organization. The representation request still requires review. Approval may connect a representative to eligible factual update tools; it does not give direct control of independent profiles, classification or editorial conclusions, or guarantee publication of a change.
Reporting an error
Use Report Listing on a Directory profile to identify inaccurate, outdated, duplicate or inappropriate information. Include the affected detail and a reliable source. For Journal or other pages, use Contact OpenViST with the page URL. Recipes also offer Propose an improvement for signed-in readers; suggestions enter a private review queue and do not change published code automatically.
Tool corrections
For a browser Tool, contact OpenViST with the tool URL, browser and a minimal anonymised example. You may also use the public source repository to inspect or suggest a correction. Never put private datasets, credentials or personal information in a public issue.
Review outcomes
OpenViST may approve, reject or request more evidence. Corrections and representation requests do not change the public record automatically. Abusive, misleading or privacy-invasive submissions may be closed without action. For questions about a request, use the contact page.
Lesson corrections
For Learn, contact OpenViST with the lesson URL, affected step, environment and a minimal example. A report is reviewed; it does not automatically alter the lesson. Do not include credentials or private data.