Skip to content

Security: toolazytoname/android-ai-stack

Security

SECURITY.md

Security policy

Never commit

  • API keys, session tokens, cookies, relay credentials, or CC Switch data.
  • A real provider base URL when it identifies a private relay.
  • Complete OpenCode or Claude configuration copied from a working device.
  • Raw evidence containing tokens, prompts, account names, or device IDs.
  • GGUF model weights.

Profiles in Git contain placeholders only. Store tokens in a separate file owned by the runtime user with mode 0600; the supplied scripts reject broader permissions.

Network defaults

Happy and local model servers bind to 127.0.0.1 by default. OpenCode Web must also remain loopback-only unless an authenticated tunnel is deliberately added. Do not expose an unauthenticated inference endpoint, Happy registration, or a development web UI to the public Internet.

Evidence

Prefer text assertions and redacted command output. Capture screenshots only when a GUI state cannot be proved otherwise. Run scripts/verify.sh before a commit; it detects common secret-shaped strings and accidental model files.

APK release identity

Installable Mobile Lab Control APKs belong in GitHub Releases, never in source history. Release APKs must match the public certificate in apps/mobile-lab-control/release-certificate.pem; its SHA-256 certificate fingerprint is D0:2C:A4:E7:A4:FB:74:7A:E4:46:92:1A:DD:19:B1:1D:83:65:EE:3E:29:30:A4:CA:2B:25:94:AB:CE:74:70:45. Do not publish a debug-signed APK as a product release. Keep the private key outside Git and back it up separately from GitHub Actions secrets.

Report a suspected vulnerability privately through GitHub's security advisory feature rather than a public issue.

There aren't any published security advisories