Skip to main content

Getting Support

Need help with Vault? There are several ways to get support and connect with the community.

GitHub Issues

The primary support channel is through GitHub Issues:

Open an Issue

Report bugs, request features, or ask questions

Before Opening an Issue

  1. Search existing issues - Your question may already be answered
  2. Check project README - Review documentation for the specific project
  3. Verify project status - Check if the project is maintained, frozen, or deprecated
  4. Gather information - Collect error messages, logs, and system details

Creating a Good Issue

When opening an issue, include:
  • Clear title - Summarize the problem or request
  • Project name - Specify which Vault project you’re using
  • Version/commit - Include the version or commit hash
  • Environment - OS, architecture, dependencies
  • Steps to reproduce - For bugs, provide detailed steps
  • Expected behavior - What should happen
  • Actual behavior - What actually happens
  • Error messages - Full error output, logs, or stack traces
  • Screenshots - If applicable

Issue Types

Bug Reports

Something isn’t working correctly

Feature Requests

Suggest new functionality

Questions

Ask for help or clarification

Documentation

Report doc issues or improvements

Community Channels

Twitter/X

Follow @maraventostudio for:
  • Project announcements
  • Updates and releases
  • Community highlights
  • Tips and tricks

Website

Visit maravento.com for:
  • Project overview
  • Additional resources
  • Contact information

Ask DeepWiki

Ask DeepWiki Use DeepWiki to:
  • Search project documentation
  • Get AI-powered answers
  • Explore code and features

Project Status

Before requesting support, check the project’s lifecycle status:
StatusBadgeSupport Level
ExperimentalexperimentalLimited - May change without notice
BetabetaActive - Testing ongoing
Release CandidateRCActive - Critical fixes only
FrozenfrozenMinimal - No planned changes
DeprecateddeprecatedNone - Obsolete
Projects marked as Frozen or Deprecated receive limited or no support. Consider using maintained alternatives.

Response Time

Please note:
  • Vault is maintained by a small team
  • Response times vary based on project status and complexity
  • Be patient and respectful
  • Community members may also help answer questions

Self-Help Resources

Documentation

  • Read the main README
  • Check individual project READMEs
  • Review this documentation site
  • Browse existing GitHub Issues

Troubleshooting

  1. Check project status - Is it maintained?
  2. Update to latest - Pull the latest commits
  3. Review dependencies - Ensure all requirements are met
  4. Check logs - Look for error messages
  5. Test minimal example - Isolate the problem
  6. Search issues - Has anyone else encountered this?

Important Notices

Non-Standard Workflow

Vault follows a non-standard workflow. Published commits may be rewritten or removed without notice as part of the debugging and improvement process.

No Pull Requests

Vault does not accept Pull Requests. All changes must be proposed via GitHub Issues.
See the Contributing page for more details.

Third-Party Components

Vault includes third-party components. For support with specific components:
  • Check component documentation
  • Contact component maintainers
  • Reference component licenses and support channels
If you find Vault useful, consider sponsoring the project: Sponsor Sponsorship helps:
  • Maintain existing projects
  • Develop new features
  • Improve documentation
  • Provide better support
  • Keep projects up-to-date

Acknowledgments

We thank all those who have contributed to this project. / Agradecemos a todos los que han contribuido con este proyecto.
The Vault project is made possible by:
  • Community contributors
  • Bug reporters and testers
  • Sponsors and donors
  • Third-party component authors

Stargazers

Join the growing community of Vault users: Stargazers

Need More Help?

If you haven’t found what you need:
  1. Open a GitHub Issue
  2. Provide detailed information
  3. Be specific about what you’ve already tried
  4. Include relevant context
The maintainers and community will do their best to help!

Build docs developers (and LLMs) love