glidejs/glide

A dependency-free JavaScript ES6 slider and carousel. It’s lightweight, flexible and fast. Designed to slide. No less, no more

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 48 minutes ago
Added to GitGenius on September 8th, 2026
Created on August 19th, 2013
Open Issues & Pull Requests: 245 (+0)
GitHub issues: Enabled
Number of forks: 758
Total Stargazers: 7,663 (+0)
Total Subscribers: 135 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 13.5 days
Mean response time: 112.0 days
90th percentile: 613.9 days
Tracked items: 27

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

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

Top labels

  • extension candidate (4)
  • feature request (1)
  • invalid (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Glide.js is a dependency-free JavaScript ES6 slider and carousel library. It solves the problem of adding carousel functionality to web pages without requiring external dependencies or bloated frameworks. The tool achieves this through a modular architecture where developers import only the functionality they need, keeping the overall footprint minimal while maintaining flexibility for customization and extension through plugins.

The project suits developers building lightweight websites or applications where bundle size matters and external dependencies should be minimized. It works well for standard carousel and slider use cases where you need reliable, straightforward sliding behavior without the overhead of larger UI frameworks. The modular design means you can strip out unused modules to reduce script weight further, and it integrates cleanly with modern bundlers like Rollup and Webpack.

Development activity shows consistent maintenance with an established test suite and linting infrastructure in place. The project maintains clear separation between bug reporting and implementation support, directing implementation questions to community channels while reserving the issue tracker for improvements and bug reports. Build tooling is well-documented with separate scripts for CSS compilation, JavaScript output variants, and comprehensive testing.