Security
Security
How to report a vulnerability, how the packages you depend on are produced, and how this site handles your account and payment.
Report a vulnerability
Email security@spawndev.com with the affected package and version, a description of the issue and, if you have one, a proof of concept. Please do not open a public GitHub issue for a vulnerability.
- We acknowledge reports within 2 business days.
- We keep you informed while we investigate and fix, and credit you in the release notes unless you prefer otherwise.
- Fixes ship as patch releases on nuget.org with the affected and fixed versions stated in the changelog.
- Paid support customers are notified of security releases directly.
Supply chain
- Open source. Every library's full source is public on GitHub, so you can audit what you ship.
- One publisher. Packages are published to nuget.org under the LostBeard account only.
- Licenses. Libraries are MIT licensed unless a package says otherwise; see open source licenses.
This website
- No passwords. Accounts sign in with passkeys (WebAuthn). There is no password database to leak.
- Payments stay with PayPal. Card and bank details are entered on PayPal and never reach our servers.
- Encrypted in transit. The site and its API are served over HTTPS only.
- Minimal data. We keep what support and billing need; see the privacy policy.