DiscordAddons is an open marketplace: there is no manual approval queue. Instead, every version of every addon goes through two separate automated checks. They answer different questions, and neither one means an addon is safe.
Before anything is published, and again whenever the source changes on GitHub, the file is downloaded through the GitHub API and checked on our servers:
*.plugin.js): the metadata header must be on the first line with @name, @author, @description and @version. The JavaScript must parse, and it must export via module.exports.*.theme.css): the metadata header is required and the CSS must parse with balanced structure.index.ts(x). The entry must export default definePlugin(...) with a name, description and authors, and every source file in the folder must parse.Submitted code is only parsed into a syntax tree. It is never executed, compiled or bundled on our servers. Size limits apply, and binary files are rejected.
The scanner (version 2026.11.1) statically inspects the code for behaviour that malicious Discord addons commonly show. Each finding has a severity:
Static scanning is not a safety guarantee. Determined attackers can evade pattern matching, and legitimate addons can trigger findings. A listing with no findings has not been reviewed by a person. Findings are published openly on every listing so you can judge for yourself.
Administrators can take down listings, clear false positives and suspend publishers. Every moderation and publishing action is recorded in an audit log. Client modifications may violate Discord’s Terms of Service. Use them at your own risk.