Skip to content

Security: AlexWhite1111/mihomo-smart-controller

Security

SECURITY.md

Security policy

Reporting a vulnerability

Open a GitHub issue only when the report contains no credentials, subscriptions, private server addresses, personal paths, state files, or browsing logs. For a report that requires sensitive evidence, first request a private reporting channel without attaching the evidence.

Sensitive local data

Treat these files as secrets:

  • any imported Mihomo or Clash YAML;
  • subscription URLs;
  • proxy usernames and passwords;
  • state.json and controller logs;
  • socket files;
  • generated runtime configuration from Clash Verge;
  • screenshots that expose node names, endpoints, or credentials.

The repository .gitignore excludes common local artifacts, but ignore rules are not a substitute for reviewing git diff --cached before every push.

Design boundary

The controller can select a member already present in Mihomo. It does not authenticate users, distribute proxy credentials, encrypt subscriptions, or protect a compromised local machine.

There aren't any published security advisories