PluginStatsFrost - Incident-aware merge protection installs statistics
By InfinitLab · GitHub Marketplace
Incident-aware merge protection. When a P1 fires, Frost guards your repos automatically
Frost - Incident-aware merge protection has 7 recorded installs on GitHub Marketplace.
It ranks #1090 of 1,393 tracked GitHub Marketplace listings by installs.
PluginStats has 1 daily observations since Oct 16, 2026; the latest is from Oct 16, 2026.
About Frost - Incident-aware merge protection
Incident-aware merge protection for GitHub.
Connect PagerDuty or incident.io and the moment a P1 fires, Frost guards your repos automatically, so the next merge doesn't make the incident worse.
Scheduled and daily protection windows are included for launches, holidays, and off-hours.
Capabilities
• Incident-Driven Protection: Connect PagerDuty or incident.io. When a P1 fires, Frost guards your repos automatically. • Daily Protection Windows: Recurring protection for off-hours, weekends, or low-capacity periods. • Scheduled Protection: Pre-declare protected periods for holidays, launches, or company events. • Override Labels: Emergency merges go through with a label and full audit trail. • Audit Logs: Compliance-ready logs of every protection event and override.
Benefits
• Keep incidents from compounding: A merge during an active P1 can turn one outage into two. Frost removes the human-in-the-loop step that gets forgotten in the chaos of incident response. • Keep shipping with confidence: Your team merges as usual on calm days. Frost guards merges only when stakes are high. • No coordination overhead: On-call doesn't have to remember to pause merges. Frost handles it the moment an incident fires.
Getting Started
Requirements: Free for public repos. Paid plans start at $29/mo for private repos. Requires GitHub org admin permissions. Docs at https://frostcode.io/docs.
Setup:
• Install Frost on your GitHub organization. • Connect PagerDuty or incident.io. Add scheduled or daily windows for predictable risk periods. • Add Frost's status check to your branch protection rules.
Common Scenarios
• Incident at 2am: PagerDuty fires a P1. Frost guards every connected repo. On-call focuses on the fix; merges wait until it resolves. • Friday afternoon deploys: Recurring daily window through Monday morning guards repos when response capacity is lowest. • Launch weeks: Mark the week around a major release as protected. Override labels let urgent fixes through.
Description from the GitHub Marketplace listing.
- Code quality
Where Frost - Incident-aware merge protection sits in the listing
Each band is one page of 20. Installs on a log scale. Placement is projected from installs, so it can differ from the marketplace's own sort order. Hover a dot to see the listing.
Charts
Images: 30d · 1y · all time · 1600×900 dark
Adoption over time
7/30/90-day growth
Filled points are observed values; hollow points come from Internet Archive snapshots of the listing page. Dashed segments span periods with no observations — values between points are not interpolated.
Recent observations
Full history (1)Similar GitHub Marketplace plugins
Data source
Install counts (installations of each GitHub App across accounts and organizations) are read from public GitHub Marketplace listing pages. GitHub does not publish ratings. Category positions reflect GitHub's own popularity sort.
Listing: https://github.com/marketplace/frost-incident-aware-merge-protection. First seen Oct 16, 2026; last successful collection Oct 16, 2026. See the methodology.