Security reporting
How to report a vulnerability in NOVI, and what to expect from us.
Last updated 19 November 2026
Draft — not yet approved
This document is a draft. It has not been reviewed by a lawyer or approved by NOVI's owner, and it will be finalised before NOVI launches publicly.Reporting a vulnerability in NOVI
If you believe you have found a security issue in the NOVI website, API or MCP server, please tell us privately through the contact page (topic “Report a security issue”) or the security email address shown there when available. Include steps to reproduce and the potential impact. Please do not publish details until we have had a reasonable chance to fix the issue.
Our commitment
- We will acknowledge your report, keep you informed and credit you if you wish.
- We will not take legal action against good-faith research that follows this policy.
Good-faith research means
- Only testing against your own account.
- Not accessing, changing or deleting other people's data.
- Not degrading the service (no denial-of-service or spam).
- Stopping and reporting as soon as you confirm an issue.
Problems with a listed project
Vulnerabilities in third-party projects should be reported to that project's maintainers. If a listing on NOVI is unsafe or misleading, use “Report a problem with this listing” on the project's page so we can review it.
How NOVI protects you
- Download links point only to official sources (the project's GitHub releases, or publisher addresses recorded by Homebrew, WinGet or Flathub), and the address is shown before you click.
- Installation commands shown are fixed, reviewed templates; text from repositories or AI is never turned into a command.
- The website cannot run anything on your computer.
- Access tokens stored only as hashes; database rules isolate each account's data.