Repository navigation
SECURITY.md — vulnerability disclosure policy #548
Description
Write SECURITY.md at the repo root. For an E2EE messaging product with on-chain funds this is a notable omission: there is currently no stated way to report a vulnerability privately, so a finder's only options are a public issue or a public PR.
Acceptance criteria:
- Gives a private reporting channel and an expected response window
- States explicitly that vulnerabilities must not be reported via public issues or PRs
- Defines scope: which components are in scope (backend, web client crypto, contracts) and what is out of scope
- Cross-links
docs/threat-model.mdso reporters know what is already a known, accepted residual risk - Notes the contract-specific path, since on-chain bugs may not be fixable by a redeploy
Activity
Scepter00 commentedon Aug 27, 2026
@Scepter00 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Scepter00 to this issue.
eischideraa-unn commentedon Aug 30, 2026
@eischideraa-unn has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @eischideraa-unn to this issue.
Deb-Auth commentedon Aug 30, 2026
@Deb-Auth has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Deb-Auth to this issue.
drips-wave commentedon Aug 30, 2026
Congratulations, @Deb-Auth! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.
🧑💻 @Deb-Auth: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
docs: add testing strategy, migration workflow, and security policy
github-actions commentedon Aug 31, 2026
Closed by #597, merged into
dev.drips-wave commentedon Aug 31, 2026
This issue has been completed by @Deb-Auth as part of the Stellar Wave Program's 8th Wave 🥳
😎 @Deb-Auth: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.