Feedback
This page says where to send feedback, questions and reports about SnapsVault, so a message reaches the right place the first time.
Where to go
| I want to | Go to |
|---|---|
| Ask a question or get help | Telegram or email hello@denodes.io |
| Give feedback or suggest a feature | GitHub issues |
| Report a bug in the Marketplace, the SnapsOS CLI, the REST API or these docs | GitHub issues |
| Report a problem with a listing or a feed file | Registry issues |
| Report a security issue | See Report a security issue. Do not open a public issue. |
Give feedback and get support
Questions about how SnapsVault works, ideas and general feedback go to the SnapsVault team on Telegram or by email at hello@denodes.io. A concrete feature request is best as a GitHub issue, because the discussion stays next to the code.
Report a bug
Open an issue in the SnapsVault repository and pick the bug template. Search existing issues first. Improvements lists what a good report contains.
Report a listing problem
A wrong value on a snapshot, a snapshot that does not appear, or a problem with a contributor's feed or registry file goes to the registry issues. Name the contributor, the chain ID and the feed URL.
A problem with a contributor's server or a snapshot file that does not download is best reported to that contributor. Its contact details are on its snapshot page in the Marketplace.
Report a security issue
Keep it private
Do not report security problems in public issues, pull requests or discussions.
Use GitHub private vulnerability reporting on the SnapsVault repository (Security tab, "Report a vulnerability"), or email hello@denodes.io. The process and the scope are in SECURITY.md.
Next steps
- Improvements: propose a change to the code, tools or docs by pull request
- Contribute snapshots: list your snapshots on SnapsVault