Skip to content

Security: erabytse/CryptoLogin

Security

SECURITY.md

Security Policy

Supported Versions

Version Supported
1.0.x
< 1.0

Reporting a Vulnerability

Please DO NOT report security vulnerabilities through public GitHub issues.

Send reports to: security@cryptologin.io

You should receive a response within 48 hours. If the issue is confirmed, we will release a patch as soon as possible.

Security Best Practices

  • Use master secrets of at least 32 characters
  • Enable HTTPS in production
  • Use rate limiting
  • Keep dependencies updated
  • Regular security audits

There aren't any published security advisories