Reporting and supply chain
Vulnerability disclosure
We take the security of Surplus and the communities it serves seriously. If you believe you've found a vulnerability, report it privately — do not open a public GitHub issue.
Please do
- Contact the Sharing Excess team directly with enough detail to reproduce
- Include affected area, steps, impact, and supporting material
- Allow reasonable time to investigate before public disclosure
Please don't
- Access, modify, or delete data that isn't yours
- Run attacks that degrade the service (denial-of-service, large-scale scanning)
- Use social engineering against staff or partners
Good-faith research within these guidelines is considered authorized.
Scope
In scope: the Surplus web application (including its API, authentication, MCP server, and file serving), its scheduled jobs, and supporting infrastructure in this platform. Underlying managed providers (Neon, Upstash, Tigris, Stripe, Resend, Cloudflare, Sentry) have their own disclosure programs.
Contact
Report to tech@sharingexcess.com. Avoid sending live credentials or large production exports in the initial email.
Dependencies and supply chain
Third-party code is managed through:
- Exact versions for the direct dependencies of every deployed service, never floating ranges
- No hand-rolled crypto — JWT via maintained libraries; passwordless auth eliminates password storage
- Parameterized database access — no string-concatenated SQL
- Managed providers for database, cache, and storage infrastructure
GitHub Dependabot runs automatically to surface known vulnerabilities. Findings are reviewed through the normal release process.
Related
- Access control — how access is controlled
- Data protection — how personal data is handled
- Infrastructure and operations — sub-processors and hosting
