We welcome contributions from the community to help improve Pangolin. To ensure your feedback is properly tracked and prioritized, please use the appropriate GitHub sections for different types of submissions.

Feature Requests

Submit in GitHub Discussions for community feedback and upvoting

Bug Reports

Submit in GitHub Issues for tracking and resolution

​
Feature Requests

Use GitHub Discussions: Pangolin Discussions
We encourage you to submit feature requests in the GitHub Discussions section of the Pangolin repository. This allows the community to:
  • Upvote features they want to see implemented
  • Provide feedback and suggestions on proposed features
  • Discuss implementation details and alternatives
  • Help prioritize which features to work on next

​
How to Submit a Feature Request

1

Check existing discussions

Search the Discussions section to see if your feature has already been requested.
2

Create a new discussion

Click “New discussion” and select “Feature Requests” or “Ideas” as the category.
3

Provide details

Include:
  • Clear description of the feature
  • Use case and benefits
  • Any implementation ideas
  • Screenshots or mockups if applicable
4

Engage with community

Respond to comments and help refine the feature proposal.

​
Feature Request Template

## Feature Request: [Brief Description]

### What problem does this solve?
[Describe the problem or limitation this feature would address]

### Proposed solution
[Describe how this feature would work]

### Use cases
[Describe specific scenarios where this would be useful]

### Additional context
[Any other relevant information, screenshots, or examples]
Feature requests with community support (upvotes and positive feedback) are more likely to be prioritized for development.

​
Bug Reports

Use GitHub Issues: Pangolin Issues
Bug reports should be submitted in the GitHub Issues section for proper tracking and resolution. This ensures:
  • Proper tracking of bugs through their lifecycle
  • Developer visibility for quick resolution
  • Version tracking and regression testing
  • Duplicate detection and consolidation

​
How to Submit a Bug Report

1

Check existing issues

Search the Issues section to see if the bug has already been reported.
2

Create a new issue

Click “New issue” and select “Bug report” as the template.
3

Fill out the template

Provide all requested information including:
  • Steps to reproduce
  • Expected vs actual behavior
  • Environment details
  • Error messages or logs
4

Add labels

Use appropriate labels to help categorize the issue.

​
Bug Report Template

## Bug Description
[Brief description of the bug]

## Steps to Reproduce
1. [First step]
2. [Second step]
3. [Third step]

## Expected Behavior
[What should happen]

## Actual Behavior
[What actually happens]

## Environment
- **Pangolin Version**: [version]
- **OS**: [operating system]
- **Browser**: [if applicable]
- **Docker Version**: [if using Docker]

## Error Messages
[Any error messages or logs]

## Additional Context
[Screenshots, configuration files, or other relevant information]
Please provide as much detail as possible to help developers reproduce and fix the issue quickly.

​
Before Submitting

  • Search existing discussions and issues to avoid duplicates
  • Provide clear, detailed information
  • Include steps to reproduce (for bugs)
  • Test on the latest version of Pangolin
  • Check if the issue is environment-specific

​
Alternative Channels

Security Issues

For security vulnerabilities, please email security@fossorial.com instead of posting publicly.

General Questions

For general questions, use GitHub Discussions with the “Q&A” category, or come chat with us on Discord.

​
Contributing Code

If you’d like to implement a feature or fix a bug yourself, please see our Development Guide for setup instructions and coding guidelines.
We appreciate all contributions, whether they’re feature requests, bug reports, or code contributions. Your feedback helps make Pangolin better for everyone.