Report it through GitHub's private vulnerability reporting on this repository, or to the maintainer directly on Discord. Include:

1. What you found — the component, route or command.
2. How to reproduce it — the smallest steps that show it.
3. What an attacker could do with it — read, change, escalate, or take down.

You can expect a first response within a few days. Fixes land on develop and ship to main in the next release — sooner, in a release of their own, when the problem is serious.

Slash and prefix commands run through one chain in src/core/checks.ts, in this order, before any command code runs:

1. Owner only — refused first for anybody not in DISCORD_OWNER_IDS, and the attempt is recorded
2. Paused — the owner console's pause stops everything
3. Blacklist — a bot-wide block on an account
4. Switched off — the command itself, the music system or the casino, in this server or everywhere
5. Server only — commands that make no sense in a DM
6. NSFW — commands kept to age-restricted channels
7. Member permissions — what the command's own Discord permission asks of the person
8. Bot permissions — what the bot needs to carry it out, named when missing
9. Cooldown — keyed per server, command and person

Owner-only commands refuse everybody else first, and say so. An attempt is logged and posted to the eval log channel. /eval checks ownership a second time inside the command, runs in a separate VM context with a five-second limit on synchronous code, posts every run with its full code, and is never reachable from the dashboard.

The dashboard is off by default. Turned on, it is guarded in layers, each with a test that was seen to fail:

The full model, and the rules that are easy to break silently, are in AGENTS.md §24.

• Give the bot only the permissions it needs. It checks its own permissions before acting and reports what is missing.
• Keep DISCORD_OWNER_IDS to accounts you control. Owner commands include /eval.
• Leave DASHBOARD_BIND at 127.0.0.1 unless a reverse proxy with HTTPS is in front of it.
• Set DASHBOARD_TRUST_PROXY=true only behind a proxy you control — trusting x-forwarded-for without one lets anyone forge their rate-limit bucket.
• Use https:// in DASHBOARD_BASE_URL once you have a certificate.
• Never commit .env. If a token leaks, reset it in the Developer Portal straight away; deleting the commit is not enough.

Snyk is continue-on-error, so a quota or permission hiccup on Snyk's side cannot fail the pipeline, and it is skipped with a notice while the SNYK_TOKEN secret is unset.

.nsprc (npm audit) and .snyk hold anything deliberately not acted on. Every entry needs three things, and an entry missing any of them should be removed:

1. Why it cannot be fixed now.
2. The version that fixes it, so there is something to wait for — or, when no release fixes it yet, the words no fixed release yet, and an expiry within 90 days instead of a year.
3. A hard expiry, so the suppression cannot rot into a permanent blind spot.

tests/config/suppressions.test.ts reads both files and fails on an entry missing any of the three.

overrides in package.json pins transitive dependencies. npm does not allow comments there, so the reasons live here. Each one should be dropped the moment its parent updates — check when a dependency bump lands.