2ndalpha/gasmask

Hosts file manager for macOS

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 14 minutes ago
Added to GitGenius on September 18th, 2026
Created on August 27th, 2013
Open Issues & Pull Requests: 87 (+0)
GitHub issues: Enabled
Number of forks: 259
Total Stargazers: 3,857 (+0)
Total Subscribers: 94 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.2 days
Mean response time: 219.0 days
90th percentile: 1313.0 days
Tracked items: 8

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,650 days
Stale 30+ days: 7
Stale 90+ days: 7

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (1)

Most active issues this week

Detailed Description

Gasmask is a hosts file manager for macOS that provides a graphical interface for managing system host entries without requiring command-line access.

The tool solves the problem of manually editing the hosts file through a text editor, which is error-prone and requires elevated privileges. Gasmask presents a user-friendly interface where developers can add, remove, and toggle host entries. The application manages multiple host groups, allowing users to switch between different sets of host configurations—useful for scenarios like testing against different servers or environments without repeatedly modifying the underlying system file.

Gasmask suits developers who frequently need to redirect domain names to different IP addresses for local development and testing. It is particularly valuable for those working with multiple projects that require different host configurations, as switching between groups is faster than manual file editing. The tool eliminates the friction of opening a text editor with sudo privileges and reduces the risk of syntax errors in the hosts file.

Development activity on the project is sparse. Commits are infrequent and appear to be concentrated in specific periods rather than distributed across time. The repository shows minimal recent engagement, with long gaps between updates. Pull requests and issues receive little attention, suggesting limited active maintenance. The codebase remains relatively unchanged over extended periods, indicating the project is not actively developed or enhanced with new features.