Skip to main content
Need help with VulnTrack? Find answers through our documentation, community channels, and issue tracking.

​
Documentation

Start with comprehensive documentation:

Getting Started

Installation, setup, and first steps with VulnTrack

Core Features

Learn about vulnerability management, scoring, and workflows

Security Frameworks

Understand DREAD, STRIDE, CVSS, and OWASP Top 10

Best Practices

Proven strategies for effective vulnerability management

FAQ

Frequently asked questions and quick answers

API Reference

Integrate VulnTrack with your security tools

​
Community Support

Get help from the VulnTrack community:

GitHub Discussions

Ask questions, share ideas, and connect with other usersBest for:
  • General questions
  • Feature ideas
  • Use case discussions
  • Showing off integrations

GitHub Issues

Report bugs and track feature requestsBest for:
  • Bug reports
  • Feature requests
  • Documentation issues
  • Technical problems
Before posting, search existing discussions and issues to see if your question has already been answered.

​
Reporting Bugs

Help improve VulnTrack by reporting issues:
1

Search Existing Issues

Check if the bug has already been reported at GitHub Issues
2

Verify on Latest Version

Confirm the bug exists in the most recent version of VulnTrack
3

Gather Information

Collect:
  • Steps to reproduce
  • Expected vs actual behavior
  • Environment details (OS, Node.js version, PostgreSQL version)
  • Screenshots or error messages
  • Relevant log output
4

Create Detailed Issue

Open a new issue with:
  • Clear, descriptive title
  • Complete reproduction steps
  • All relevant information
  • Code samples if applicable
See the FAQ for common issues and solutions before reporting.

​
Feature Requests

Suggest new features or improvements:
1

Check Roadmap

Review the Changelog to see if it’s already planned
2

Search Discussions

Look for similar ideas in GitHub Discussions
3

Describe Your Use Case

Explain:
  • What problem you’re trying to solve
  • How you currently work around it
  • How the feature would help
  • Any examples from other tools
4

Engage with Feedback

Respond to questions and feedback from maintainers and community

​
Getting Help

​
Before Asking

  1. Read the documentation - Most questions are answered here
  2. Check the FAQ - Common issues and solutions
  3. Search existing discussions - Someone may have asked already
  4. Review the changelog - Recent updates may address your question

​
Asking Good Questions

Get better answers by providing:
  • Clear problem description - What are you trying to accomplish?
  • What you’ve tried - Show your debugging steps
  • Environment details - Version, OS, configuration
  • Code samples - Minimal reproducible example
  • Error messages - Complete, unmodified output
Never share sensitive information (passwords, API keys, vulnerability details) in public discussions.

​
VulnTrack Research

Learn from in-depth technical guides:

OWASP Top 10 2024 Analysis

Deep dive into the most critical web application security risks

DREAD vs CVSS Strategy

Choose the right scoring framework for your organization

Threat Modeling Guides

Practical approaches to identifying and categorizing threats

Case Studies

Real-world vulnerability analysis and remediation stories
VulnTrack Research content is built into the application and accessible from the dashboard.

​
Contributing

Help make VulnTrack better for everyone:
  • Code Contributions - Fix bugs or add features
  • Documentation - Improve guides and examples
  • Testing - Verify issues and test pull requests
  • Community Support - Answer questions in discussions
  • Integrations - Build and share tool integrations
See the Contributing Guide for detailed information.

​
Security Issues

Do not report security vulnerabilities through public GitHub issues. For security concerns:
  1. Email maintainers directly - Contact information in GitHub profile
  2. Provide detailed information - Steps to reproduce, impact assessment
  3. Allow time for response - Give maintainers time to address issue
  4. Coordinate disclosure - Work together on responsible disclosure
Public disclosure of security vulnerabilities before fixes are available puts all VulnTrack users at risk.

​
Commercial Support

VulnTrack is a community-driven open source project. Commercial support options may be available in the future. For now:
  • Community support through GitHub Discussions
  • Self-service documentation and guides
  • Community-contributed integrations and scripts

​
Response Times

This is an open source project maintained by volunteers:
  • Critical bugs: Best effort, usually within days
  • General issues: Depends on maintainer availability
  • Feature requests: May take weeks or months to implement
  • Documentation: Often addressed quickly
Contributing to VulnTrack is the fastest way to get features you need. See the Contributing Guide to get started.
ResourceURLPurpose
GitHub Repositorygithub.com/ogdmerlin/vulntrackSource code and releases
GitHub Issuesgithub.com/ogdmerlin/vulntrack/issuesBug tracking
GitHub Discussionsgithub.com/ogdmerlin/vulntrack/discussionsCommunity help
DocumentationThis siteGuides and reference
LicenseMIT LicenseUsage terms

​
Feedback

Your feedback helps improve VulnTrack:
  • What’s working well? - Share success stories
  • What’s confusing? - Help us improve documentation
  • What’s missing? - Suggest new features
  • What’s broken? - Report bugs
Share feedback through:
  • GitHub Discussions for general feedback
  • GitHub Issues for specific problems
  • Pull requests for direct improvements
VulnTrack is built by and for the security community. Your input shapes the future of the platform.

​
Thank You

Thank you for using VulnTrack and supporting open source security tools. Together we’re building better vulnerability management for everyone.

Build docs developers (and LLMs) love

Get started for freeTalk to us