emilkowalski/vaul

A drawer component for React.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 52 minutes ago
Added to GitGenius on September 7th, 2026
Created on July 16th, 2023
Open Issues & Pull Requests: 164 (+0)
GitHub issues: Enabled
Number of forks: 368
Total Stargazers: 8,600 (+0)
Total Subscribers: 17 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.1 days
Mean response time: 30.1 days
90th percentile: 103.1 days
Tracked items: 200

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 2% of issues opened in the past year have been closed. Three people close 82% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 124
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 538 days
Stale 30+ days: 115
Stale 90+ days: 112

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

Detailed Description

Vaul is a drawer component for React that provides a reusable UI element for displaying content in a sliding panel.

The tool solves the problem of implementing drawer interfaces in React applications by offering a pre-built component that handles the common patterns of drawer behavior. It abstracts away the complexity of managing drawer state, animations, and interactions, allowing developers to integrate drawer functionality without building from scratch.

Vaul suits projects that need drawer components as part of their UI toolkit, particularly those built with React where developers want to avoid reinventing this interaction pattern. It works well for applications requiring modal-like panels that slide in from the edge of the screen, such as navigation menus, settings panels, or supplementary content displays.

The project is unmaintained and the author has indicated they do not plan to actively develop it in the near future, describing it as a hobby project they lack time and motivation to work on currently. Developers considering adoption should be aware that they would be responsible for maintaining and updating the codebase themselves, with no expectation of ongoing support or bug fixes from the original author.