googlechrome/chrome-extensions-samples

Chrome Extensions Samples

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 8 minutes ago
Added to GitGenius on September 3rd, 2026
Created on June 13th, 2012
Open Issues & Pull Requests: 54 (+0)
GitHub issues: Enabled
Number of forks: 9,015
Total Stargazers: 17,753 (+0)
Total Subscribers: 709 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.2 hours
Mean response time: 28.4 days
90th percentile: 77.0 days
Tracked items: 78

How this project is maintained

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

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

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

Top labels

  • new sample (2)
  • P0 (1)
  • enhancement (1)

Most active issues this week

Detailed Description

Chrome Extensions Samples is a collection of official code examples for building Chrome Extensions and the Chrome Apps platform.

The repository addresses the need for developers to learn how to build extensions by providing working sample code organized by scope and API coverage. Developers can explore single-API focused samples in the api-samples directory or examine full-featured extensions that span multiple APIs in the functional-samples directory. The samples cover manifest configuration, content scripts, background scripts, popup interfaces, and other core extension development patterns. Installation involves cloning the repository and loading samples as unpacked extensions during development. The project also maintains archived resources for the deprecated Manifest Version 2 and Chrome Apps platform.

Developers building their first extension or learning specific Chrome APIs should use these samples as reference implementations. The repository suits anyone needing concrete examples of how to structure an extension, configure permissions, or implement particular browser capabilities. The project's homepage links to the Chrome Developers documentation, positioning these samples as the official companion to the platform's reference materials.

The maintainers respond to issues and pull requests within a day.