microsoft/playwright-python

Python version of the Playwright testing and automation library.

Owned by Microsoft

View on GitHub ↗Jump to charts ↓Open shareable report →

microsoft/playwright-python has 15k+ stars and 1k+ forks on GitHub, is written in Python, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 5 minutes ago
Added to GitGenius on September 3rd, 2026
Created on July 1st, 2020
Open Issues & Pull Requests: 4 (+0)
GitHub issues: Enabled
Number of forks: 1,250
Total Stargazers: 15,046 (+0)
Total Subscribers: 155 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 15.1 hours
Mean response time: 38.4 days
90th percentile: 70.5 days
Tracked items: 327

Maintainer activity

2 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 3% of issues opened in the past year have never received a reply. Work labelled "triaging" is answered fastest, typically in about 9 hours, while "P3-collecting-feedback" waits about 4 days. 97% of issues opened in the past year have since been closed. Three people close 80% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

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

Top labels

  • P3-collecting-feedback (43)
  • triaging (27)
  • v1.49 (6)
  • v1.50 (3)
  • v1.52 (2)
  • v1.32 (1)
  • v1.48 (1)
  • v1.51 (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Playwright for Python is a browser automation library that enables testing and scripting of web applications across multiple browsers with a single API.

The tool addresses the need to automate interactions with web browsers for testing, scraping, and validation purposes. It works by providing a unified interface to control Chromium, Firefox, and WebKit browsers across Linux, macOS, and Windows. Rather than requiring separate code paths for each browser, developers write once and the library handles browser-specific differences internally. The library emphasizes being ever-green, meaning it automatically updates to compatible browser versions, capable with support for modern web features, reliable through consistent behavior across browsers, and fast through optimized automation protocols.

Developers should choose this tool when they need cross-browser testing or automation without maintaining browser-specific code branches. It suits projects ranging from end-to-end testing suites to web scraping tasks where browser interaction is required. The project is particularly valuable for teams already invested in the Python ecosystem who want to avoid learning JavaScript or other languages to access browser automation capabilities. The availability of Playwright in Node.js, .NET, and Java means teams can standardize on the same testing patterns across polyglot environments, though each language implementation is maintained separately.

The project shows sustained development activity with regular updates to browser version support and API refinements. The maintainers actively engage with the community through documented communication channels and respond to issues and feature requests. The codebase receives consistent attention to compatibility across the three major browser engines, ensuring that automation code written for one browser works reliably on the others. Documentation is comprehensive and kept current alongside library releases.