google/security-research

This project hosts security advisories and their accompanying proof-of-concepts related to research conducted at Google which impact non-Google owned code.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 14th, 2026
Created on June 15th, 2020
Open Issues & Pull Requests: 93 (+0)
GitHub issues: Enabled
Number of forks: 583
Total Stargazers: 4,643 (+0)
Total Subscribers: 214 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.1 days
Mean response time: 79.9 days
90th percentile: 292.0 days
Tracked items: 25

Most active contributors

Sign in to see contributor activity.

How this project is maintained

86% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 75% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 21
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 479 days
Stale 30+ days: 19
Stale 90+ days: 16

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

Detailed Description

Security Research is a repository that hosts security advisories and proof-of-concept code for vulnerabilities discovered by Google researchers in non-Google software.

The repository addresses the need for responsible vulnerability disclosure by publishing security research findings alongside working exploits. Google's approach follows a 90-day disclosure deadline: vendors are notified immediately with full details, and findings are shared publicly after 90 days or sooner if a vendor releases a fix. This model aims to balance researcher transparency with vendor remediation time, giving the defensive community access to vulnerability information while allowing maintainers reasonable opportunity to patch.

The repository serves security researchers, vulnerability analysts, and developers who need to understand real-world attack vectors and proof-of-concept implementations. It is suited for anyone studying vulnerability patterns, evaluating their own software's security posture, or learning from Google's security research methodology. The advisories are browsable through the repository's security advisories page, making it accessible for reference and education rather than as a dependency to integrate into projects.

The project maintains a curated collection of published advisories with accompanying code, accepting contributions primarily in the form of corrections to existing patches. Development activity centers on the publication and maintenance of security research findings rather than rapid feature iteration or frequent releases.