chromedp code examples.
1.3k
Stars
240
Forks
2
Open issues
11
Contributors
AI Analysis
This repository provides a curated collection of practical code examples demonstrating how to use chromedp, a headless browser automation library for Go. It serves developers building web scraping, testing, and browser automation tools who need reference implementations for common tasks like clicking, form submission, PDF generation, and device emulation. Not suitable for those seeking a complete browser automation framework—this is a companion to the chromedp library itself.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Chromedp examples: curated Go automation scripts for browser automation learning
This is a companion examples repository for chromedp, a Go library that controls Chrome/Chromium via the DevTools protocol. It contains 23 worked examples covering common headless browser tasks: clicking, form submission, PDF generation, screenshot capture, JavaScript evaluation, and proxy authentication. Primarily used as a learning resource and reference implementation for developers adopting chromedp, not a standalone tool. Adoption appears limited to chromedp users who need concrete code samples.
Created December 2017 as the chromedp library matured and needed reference examples. It evolved in parallel with chromedp's development, providing practical demonstrations of the library's capabilities. The examples repository serves as the official companion to the core chromedp project.
1,261 stars accumulated over ~8.5 years represents modest but stable interest. Zero stars gained in the last 7 days and an infrequent push cadence (last update today, but likely maintenance rather than feature development) suggests the repository has reached a stable state. Growth appears driven by chromedp adoption rather than independent momentum. Fork rate (240 forks) indicates some developer customization for local use cases.
Adoption not verified at scale. This is a examples-only repository without documented case studies or production deployment metrics. Usage is likely confined to developers learning chromedp or prototyping automation workflows. No telemetry, no known institutional adopters mentioned.
Based on README, the repository appears to be organized as a flat collection of self-contained example programs, each in its own directory with a main.go file. Examples are built as standalone executables using Go's standard build tooling. No shared framework or abstraction layer is documented; each example likely demonstrates specific chromedp API patterns in isolation.
Not documented in README. No mention of automated tests, test fixtures, or CI pipelines for verifying examples remain functional.
Last push 2026-07-06 (today relative to analysis date) indicates active maintenance. However, the README explicitly acknowledges that 'examples may break occasionally' when target websites change, and that selectors may become stale. This is a realistic constraint for web scraping examples, not a maintenance failure. Update frequency appears tied to breaking changes rather than regular development cycles.
ADOPT IF: you are learning chromedp or need reference implementations of common browser automation patterns in Go; you value focused, practical examples over exhaustive coverage. AVOID IF: you need comprehensive, guaranteed-working examples across many websites (README warns that selectors break when sites change); you require automated test coverage for the examples themselves; you prefer language-agnostic automation tools. MONITOR IF: you are evaluating chromedp for a new project and want to assess the quality and breadth of available examples before committing.
Independent dimensions
Mainstream potential
2/10
Technical importance
5/10
Adoption evidence
3/10
- Examples frequently break when target websites change layout or selectors, as documented in README; maintenance burden falls on community contributors.
- No automated testing of examples means bitrot is discovered through user reports rather than CI, leading to potential outdated or non-functional samples.
- Repository depends entirely on chromedp adoption; if chromedp falls behind competing libraries (Playwright, Puppeteer), examples may become less relevant.
- Learning-focused examples may oversimplify error handling, timeouts, or production-hardening patterns, leading developers to copy-paste fragile code.
- Update lag: examples may lag behind new chromedp API features, leaving users without reference code for newer capabilities.
Repository will remain stable and low-activity, serving as a passive reference resource for chromedp users. Unlikely to see rapid growth or significant feature expansion. Maintenance will be reactive (fixing broken examples when reported) rather than proactive. Success measured by continued relevance to chromedp community, not by independent adoption.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- Go
- License
- MIT
- Last updated
- 5d ago
- Created
- 104mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
No open issues — clean slate.
Top contributors
Recent releases
No releases published yet.
Similar repos
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
chromedp/examples
this
|
1.3k | — | Go | 7/10 | 5d ago |
|
chromedp/chromedp
|
13.2k | — | Go | 8/10 | 4mo ago |
 puppeteer/examples
|
2.4k | — | JavaScript | 7/10 | 3w ago |
 go-rod/rod
|
7k | — | Go | 8/10 | 2mo ago |
 chrome-php/chrome
|
2.7k | — | PHP | 8/10 | 4d ago |
 GoogleChrome/samples
|
5.9k | — | JavaScript | 7/10 | 15h ago |
Selenium is more mature and language-agnostic, but chromedp examples focus specifically on Chrome DevTools protocol with lower overhead; Selenium has larger ecosystem of examples and tutorials.
Playwright examples are more polished and cross-browser, but chromedp is lighter-weight and Go-native; chromedp examples are smaller in number but focused on direct Chrome automation.
Puppeteer has significantly more examples and broader adoption in JavaScript; chromedp examples serve Go developers specifically and are smaller in scope.
Colly is simpler for static HTML parsing, but chromedp handles JavaScript-heavy sites; examples target different use cases.
Direct Chrome CLI is minimal but requires manual protocol handling; chromedp examples abstract that complexity with library integration.