postcss/autoprefixer

Parse CSS and add vendor prefixes to rules by Can I Use

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 30 minutes ago
Added to GitGenius on September 2nd, 2026
Created on March 14th, 2013
Open Issues & Pull Requests: 39 (+0)
GitHub issues: Enabled
Number of forks: 1,286
Total Stargazers: 22,231 (+0)
Total Subscribers: 361 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.1 hours
Mean response time: 13.6 hours
90th percentile: 16.4 hours
Tracked items: 25

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 11% of issues opened in the past year have been closed. Three people close 100% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 2,099 days
Stale 30+ days: 4
Stale 90+ days: 3

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 (2)
  • support (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Autoprefixer is a PostCSS plugin that parses CSS and automatically adds vendor prefixes to rules based on browser compatibility data from Can I Use.

The tool solves the problem of manually tracking which CSS properties require vendor prefixes across different browsers and versions. It works by analyzing your CSS rules and inserting the necessary prefixes such as -webkit-, -moz-, and -ms- where needed. The plugin uses Can I Use data to determine which prefixes are required for your target browsers, allowing you to write standard CSS without worrying about browser-specific variants.

Autoprefixer suits projects of any size that need to maintain broad browser compatibility without the maintenance burden of hand-writing prefixes. It integrates into build pipelines as a PostCSS plugin, making it straightforward to add to existing workflows. The tool is particularly valuable for teams that want to define their browser support targets once and have prefixes applied consistently across the entire codebase.

The project maintains active engagement with its user base through issue responses and pull request reviews. Development follows a pattern of regular updates that keep pace with changes in browser support and CSS specifications. The maintainers respond to reported bugs and feature requests, indicating ongoing stewardship of the tool's reliability and relevance.