hammerjs/hammer.js

A javascript library for multi-touch gestures :// You can touch this

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 60 minutes ago
Added to GitGenius on September 2nd, 2026
Created on March 2nd, 2012
Open Issues & Pull Requests: 317 (+0)
GitHub issues: Enabled
Number of forks: 2,557
Total Stargazers: 24,343 (+0)
Total Subscribers: 511 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 24.8 days
Mean response time: 237.2 days
90th percentile: 213.2 days
Tracked items: 15

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

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

Top labels

  • Firefox (1)
  • bug (1)
  • enhancement (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Hammer.js is a JavaScript library for recognizing multi-touch gestures. It abstracts away the complexity of handling touch events across different devices and browsers, providing a unified API for detecting gestures like tap, swipe, pinch, and rotate. Rather than requiring developers to manually track touch points and calculate distances or angles, the library handles the low-level event processing and gesture recognition logic, letting developers attach simple listeners to gesture events on DOM elements.

The library suits projects that need reliable touch interaction support, particularly on mobile devices and tablets where multi-touch is common. It works well for applications requiring gesture-driven interfaces, from mobile web apps to interactive visualizations. Developers building responsive web experiences that must work across varied touch-capable devices will find value in the abstraction it provides, avoiding the need to reimplement gesture detection for each project.

The project maintains active engagement with its codebase, incorporating feedback and addressing issues raised by users. Development shows consistent attention to the library's core functionality and compatibility concerns. The maintainers respond to community contributions and work to keep the tool functional across evolving browser environments.