Skip to content

Security: hetaoBackend/mcode-passport

SECURITY.md

Security Policy

Supported versions

The latest released minor version receives security fixes. The project is currently alpha, so users should review release notes before upgrading.

Threat model

mcode-passport handles OAuth access and refresh tokens. It is designed for one local OS user on a trusted workstation.

  • The gateway binds to 127.0.0.1 only.
  • Every inference and shutdown request requires a random 256-bit bearer token.
  • Credential and settings files use mode 0600; their directory uses 0700 on Unix.
  • Credential updates use atomic replacement and a cross-process lock.
  • The health endpoint exposes provider ids but no token, account id, prompt, or response.
  • Remote image URLs are rejected; only inline base64 data URLs are accepted.
  • No telemetry or remote control plane is included.

This does not protect a user from malware or another process already running with the same OS account. Treat the MiniMax data directory as sensitive and do not sync it to public storage.

Logs

The gateway does not intentionally log prompts or credentials. Avoid adding request bodies, authorization headers, OAuth events, or provider payloads to logs when contributing.

Reporting a vulnerability

Do not open a public issue for a credential leak or remotely exploitable vulnerability. Use GitHub private vulnerability reporting for this repository. Include affected versions, reproduction steps, impact, and any proposed mitigation.

If private reporting is unavailable, open a minimal issue asking the maintainer to enable a private security channel; do not include exploit details or secrets.

Subscription policies

This project does not bypass quotas, geographic restrictions, account controls, or vendor terms. Users are responsible for confirming that a subscription may be used through a third-party local client. Anthropic subscription support is explicitly experimental.

There aren't any published security advisories