For creators
Your project has a page on Modgrade. Here is how we build it, and what to do if something on it is wrong.
1. Which files we check
We download your project's current files from Modrinth and CurseForge: the newest release or beta for each Minecraft version and loader. We compare them with known malware, then our own tools read their code in a deep check. Every other file is listed in Releases with its own result.
2. What the results mean
Passed Our checks found nothing harmful in the current files.
Partly checked Nothing harmful found in the parts we could check. Some files are not checked yet, or some files packed inside could not be read.
Warning We found something that could be risky, for example code downloaded over plain http or an address hidden in the code. It is not proof of malware, and the download stays available.
Malware We found code that steals accounts or passwords, runs hidden programs or destroys data. The download is blocked.
Not checked We have not checked the files yet, or their author does not let other sites download them from CurseForge.
Every result shows what it is based on: the files, the lines of code and the addresses. How it works has more detail.
3. Files CurseForge does not let us download
On CurseForge, creators can choose to block other sites from downloading their files. When they do, we cannot check them. If none of your files can be downloaded, your page shows Not checked. If some can, it shows Partly checked and says how many cannot be checked. It is a setting, not a sign that anything is wrong. To have your files checked, allow other sites to download them, or drop your file into the Scanner: it is checked like any other file.
4. Privacy and AI
Privacy lists the web addresses we find in your code and what it sends to them. Checking for updates on Modrinth or CurseForge is not counted as sending data about the player. AI shows the evidence of AI use we find: in the Modrinth form, your texts, your code history or the metadata of your images. It is a fact, not a judgment, and it is never shown as a label in the lists. Bots that review pull requests and AI instruction files do not count.
5. If a result is wrong
Use the "Wrong result? Tell us" link under the Security, Privacy or AI answer when you see it, or the contact form with "I made this project". Tell us which file it is and what its code does. We read every message, check the file again, and correct the page when we were wrong.
6. Fixing a finding
A Warning names the code that caused it. When you change that code and publish a new version, we check the new files, usually within a day. Older files keep their own result in Releases.