ampproject/amphtml

The AMP web component framework.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 16 minutes ago
Added to GitGenius on September 3rd, 2026
Created on September 1st, 2015
Open Issues & Pull Requests: 1,027 (+0)
GitHub issues: Enabled
Number of forks: 4,057
Total Stargazers: 14,904 (+0)
Total Subscribers: 614 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 18.1 hours
Mean response time: 40.1 days
90th percentile: 49.8 days
Tracked items: 430

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 87% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "WG: stories" is answered fastest, typically in under an hour, while "P1: High Priority" waits about 31 hours. Only 6% of issues opened in the past year have been closed. Three people close 59% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 501
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 1,613 days
Stale 30+ days: 496
Stale 90+ days: 496

Recent activity

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

Top labels

  • Stale (366)
  • Type: Bug (292)
  • Type: Feature Request (170)
  • WG: components (152)
  • P3: When Possible (120)
  • P2: Soon (89)
  • WG: stories (79)
  • P1: High Priority (48)

Most active issues this week

Detailed Description

AMP is a web component framework for building user-first websites, stories, ads, emails, and other web experiences with a focus on performance and user experience.

AMP addresses the problem of creating fast, reliable web content by providing a component-based framework that enforces performance best practices at the platform level. The framework includes pre-built components for common web elements and patterns, allowing developers to build rich experiences while maintaining strict performance constraints. The approach works by validating AMP documents against a set of rules that prevent slow-loading patterns and encourage mobile-first design.

Developers should choose AMP when building content-heavy sites, publisher platforms, or advertising experiences where performance and user experience are critical priorities. The framework is particularly suited to news sites, blogs, e-commerce product pages, and email campaigns. The project provides extensive learning resources including guides, tutorials, examples, reference documentation, and templates on its main site. Support is available through Stack Overflow and the project's support page for developers encountering issues.

The project maintains active community engagement through multiple channels including Slack participation, weekly design reviews, and organized working groups where most day-to-day development occurs. The team explicitly welcomes new open source contributors regardless of prior experience and provides structured onboarding documentation. The project publishes a public roadmap detailing significant ongoing work and maintains detailed release documentation explaining version schedules and change tracking. Security vulnerabilities are handled through a responsible disclosure program with Google's Application Security team.