mitchellh/vouch

A community trust management system based on explicit vouches to participate.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 58 minutes ago
Added to GitGenius on September 13th, 2026
Created on February 5th, 2026
Open Issues & Pull Requests: 16 (+0)
GitHub issues: Enabled
Number of forks: 93
Total Stargazers: 5,099 (+0)
Total Subscribers: 14 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Vouch is a community trust management system that controls participation in projects through explicit vouches and denunciations.

The system addresses the problem of low-quality contributions by establishing an explicit trust model where maintainers and trusted community members can vouch for others before they gain access to certain project areas. Rather than relying solely on the historical barrier of effort to filter contributors, vouch creates a configurable gating mechanism. The vouch list is stored in a single flat file using a minimal format that can be parsed with standard POSIX tools and any programming language without external dependencies.

Projects adopting vouch have complete control over who gets vouched, how vouching works, what consequences vouching carries, and which parts of the project require vouching. The system is generic enough for any project on any code forge, though GitHub integration is provided out of the box through GitHub Actions and a CLI tool. This flexibility means each project can implement a policy suited to its own community and needs. The tool is particularly relevant for projects experiencing high volumes of AI-generated or low-effort contributions that bypass traditional review filters.

The project maintains active development with regular improvements based on real-world usage. The codebase is written in Nushell and includes comprehensive documentation through a FAQ and cookbook. The system is in experimental use by established projects, with the maintainers continuing to refine it based on feedback from those deployments.