Currently, only the latest version of Ampdeck+ is supported with security updates.
| Version | Supported |
|---|---|
| 2.0.x | ✅ |
| < 2.0 | ❌ |
If you discover a security vulnerability in Ampdeck+, please report it responsibly:
- Do NOT open a public GitHub issue for security vulnerabilities
- Email the maintainer directly at 155098676+DreadHeadHippy@users.noreply.github.com
- Include the following information:
- Description of the vulnerability
- Steps to reproduce the issue
- Potential impact
- Any suggested fixes (if applicable)
- Response Time: You can expect an initial response within 48 hours
- Updates: We'll keep you informed about the progress of fixing the vulnerability
- Disclosure: Once the vulnerability is fixed, we'll work with you on coordinated disclosure
- Credit: If you wish, we'll credit you in the release notes for responsibly disclosing the issue
Ampdeck+ stores your Plex authentication token locally in the Stream Deck configuration. This token provides access to your Plex account:
- Tokens are stored in Stream Deck's secure settings storage
- Never share your configuration files with untrusted parties
- Debug logs automatically sanitize tokens before output
- All communication with Plex servers uses the credentials you provide
- The plugin connects to your local Plexamp instance and Plex server
- No data is transmitted to third parties
- All API calls are made directly to your Plex infrastructure
- Only download Ampdeck+ from official sources (GitHub releases or Elgato Marketplace)
- Keep your Plex token secure and never share it publicly
- Use debug logging only when troubleshooting (tokens are sanitized, but other sensitive info may appear)
- Regularly update to the latest version for security patches
Ampdeck+ uses minimal dependencies. Security updates for dependencies are monitored and applied promptly. You can audit dependencies by checking package.json.
Thank you for helping keep Ampdeck+ and its users safe!