Corrections policy
AgentHubStack welcomes specific, evidence-based correction requests. For an error tied to a public repository, use /submit with the relevant repository URL and explain the disputed statement in the note field.
How to report an issue
- Provide the public repository URL associated with the listing.
- Identify the page and the exact statement, field, or score signal you believe is wrong.
- Link to current public evidence and explain what should change.
- Do not send secrets, private repository content, personal data, vulnerability exploitation details, or credentials through the submission form.
How reports are reviewed
The AgentHubStack Editorial Team compares the report with current public evidence and the methodology used by the page. We may update the content, add context, leave it unchanged, or remove a listing when that is the clearest outcome.
What counts as a correction
Corrections address verifiable factual errors, materially stale information, broken identity or repository links, inaccurate attribution, and score inputs that no longer match public evidence.
- A preference, promotional request, or disagreement with editorial judgment is not automatically a factual correction.
- A maintainer statement may be relevant evidence, but it is not always independently verifiable.
- We cannot verify claims that depend only on private repositories or confidential material.
Timing and records
We do not promise a response or resolution time. Material changes may be incorporated directly into the page. This public policy does not claim that a complete public change log is maintained for every edit.
Security reports
The general submission form is not a secure vulnerability-reporting channel. Do not include exploit details or sensitive data. Report vulnerabilities in a listed project through that project's published security process. AgentHubStack does not claim to receive private repository access for correction review.