pilotmoon/scroll-reverser

Per-device scrolling prefs on macOS.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 14 minutes ago
Added to GitGenius on September 19th, 2026
Created on October 26th, 2011
Open Issues & Pull Requests: 50 (+0)
GitHub issues: Enabled
Number of forks: 173
Total Stargazers: 3,603 (+0)
Total Subscribers: 22 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 16.3 hours
Mean response time: 142.7 days
90th percentile: 442.8 days
Tracked items: 12

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 13
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 885 days
Stale 30+ days: 11
Stale 90+ days: 11

Recent activity

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

Top labels

  • bug (2)
  • feature (2)
  • can't fix (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Scroll Reverser is a macOS utility that lets you configure scrolling direction independently for each input device.

The problem it solves is that macOS applies a single scrolling direction setting globally across all input devices. Scroll Reverser allows you to set different scrolling preferences per device, so you can have natural scrolling enabled for a trackpad while keeping traditional scrolling for a mouse, or any other combination. The tool runs as a background service that intercepts scroll events and applies device-specific rules before they reach applications.

The tool suits anyone using multiple input devices on macOS who finds the global scrolling setting incompatible with their workflow. It is particularly valuable for users who switch between trackpads and mice frequently, or who use external pointing devices that feel more natural with reversed scrolling. Since the tool operates at the system level, it works transparently with all applications without requiring per-app configuration.

Development on the project is sparse, with infrequent commits and minimal recent activity. The codebase remains small and focused, with no evidence of active feature expansion or regular maintenance cycles. Issues and pull requests receive responses, but the pace of development suggests this is a stable, mature tool rather than one under active development.