Closed beta
The firewall for your OSS projects
Trigger workflows from contributor activity. Keep the good, reject the bad.
Screen every PR before it hits main.
See a detailed log of events such as PR creation, or comments. Events can be displayed by severity, type, or time, whatever makes sense to you.
Join the beta to see it live
Ingest. Evaluate. Act.
Account age, rate limits, hidden links, max files changed; get multiple composable rules in one workflow.
Org members are exempt and there's evidence on every run.
Create custom workflows.
Triggers, rules, gates, actions. all-of / any-of. needs_review pauses for moderation.
Every run snapshots the definition so history stays honest.
One comment. One check. Zero noise.
One sentence explanations. Maintainers can view a detailed explanation on Tripwire. Contributors never get an essay.
Claim your spot on the waitlist
Block noise. Pass signal.
Install the GitHub App. Workflows evaluate every change request. Runs are public; deciding stays gated.
Questions & Answers
Everything you need to know about tripwire
Install the GitHub App and Tripwire starts ingesting contributor activity — change requests, comments, and the rest. Every event runs through your workflows: triggers fire, rules evaluate, actions decide. Runs are public; deciding stays gated.
Org members. Their change requests skip rule evaluation entirely — everyone else gets screened. Either way the run keeps its evidence, so you can always see why a decision was made.
The change request gets one check and one comment: this change request can't be merged. The public run page lists every rule that was evaluated — say 3 blocked, 3 passed — with the evidence behind each finding. Maintainers get the detail; contributors get one sentence.
