Browser extension for viewing archived and cached versions of web pages, available for Chrome, Edge and Safari
1.6k
Stars
122
Forks
28
Open issues
1
Contributors
AI Analysis
Web Archives is a browser extension that finds archived and cached versions of web pages across multiple archive sources, integrated into context menus and toolbars. It serves users who need to recover deleted or inaccessible web content, and benefits researchers, archivists, and casual users investigating page history. It is not a general-purpose browsing tool but rather a specialized utility for archive access.
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.
Lightweight browser extension for accessing archived and cached web pages across multiple sources
Web Archives is a cross-browser extension (Chrome, Firefox, Edge, Safari, Opera) that surfaces archived and cached versions of web pages from multiple archive services. It solves the practical problem of link rot—finding content when the live page is down, removed, or changed—by aggregating search across services like the Wayback Machine, Google Cache, and others. Adoption appears modest but stable; real-world usage evidence is limited to store ratings and GitHub metrics, but the extension has maintained active development over 9 years with regular updates through mid-2026.
Created in August 2017 by dessant, the extension emerged during growing awareness of web fragility and link decay. It filled a gap for users wanting quick, browser-integrated access to archives without visiting multiple sites separately. The project has evolved to support five browsers and multiple archive sources, suggesting responsive maintenance rather than feature-driven growth.
Star growth is modest (~1,571 stars as of mid-2026, gaining 3 in the last week), suggesting saturation in a niche use case rather than explosive adoption. The extension's practical utility—restoring lost pages—appeals to researchers, journalists, and information workers, but this is inherently a smaller user segment than general productivity tools. Recent push activity (2026-06-27) confirms ongoing maintenance, but growth appears stable rather than accelerating.
Adoption not verified through concrete metrics. The extension is distributed across five official store platforms (Chrome, Firefox, Edge, Safari, Opera), indicating successful submission and approval, but store review counts are not provided in README. GitHub metrics alone (1,571 stars, 122 forks) suggest hobbyist-to-moderate interest. No case studies, enterprise deployment evidence, or published user surveys are mentioned.
Likely a modular browser extension built in JavaScript with per-browser packaging (Chrome, Firefox, Edge, Safari, Opera). Based on README, the extension integrates a context menu and toolbar UI, manages user-configurable archive sources, and orchestrates searches across multiple backends. Architecture appears service-agnostic, allowing toggle and reordering of archive sources.
Not documented in README. No mention of test suite, CI/CD pipeline, or testing strategy visible in provided metadata.
Last push 2026-06-27 (10 days before analysis date) indicates active maintenance. Project has survived 9 years without abandonment. Update cadence appears regular but not aggressive; this suggests stability-focused maintenance rather than rapid feature development. GPLv3 licensing and multi-year copyright notice (2017-2026) confirm sustained stewardship.
ADOPT IF: you are a researcher, journalist, or knowledge worker who frequently encounters broken links and wants instant access to archived versions without context-switching. AVOID IF: you need programmatic/headless archive access, self-hosted solutions, or large-scale batch archiving—use ArchiveBox or wabarc instead. MONITOR IF: you are considering it for team deployment; adoption metrics remain opaque, and there is no documented enterprise support or SLA.
Independent dimensions
Mainstream potential
3/10
Technical importance
5/10
Adoption evidence
4/10
- Adoption metrics are not publicly visible; cannot confirm actual user base beyond GitHub metrics, which may inflate or misrepresent engagement.
- Dependency on third-party archive services (Wayback Machine, Google Cache, etc.) means outages or API changes could degrade functionality; no fallback or redundancy strategy is documented.
- Test coverage and code review practices are not documented; long maintenance intervals between updates could indicate low velocity or difficulty shipping changes.
- Browser extension stores (Chrome, Firefox, Microsoft, Apple) each have different policies and review cycles; any change to extension policies could disrupt availability.
- Limited documentation of configuration, API coverage, or troubleshooting; users encountering issues may have few resources beyond GitHub issues.
Likely to remain a stable, niche utility with slow growth. No signs of acceleration or mainstream adoption; use case (link restoration) is valuable but narrow. May be absorbed into other productivity tools or slowly accumulated by a larger ecosystem project, but standalone deployment will probably persist as long as dessant maintains it.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- JavaScript
- License
- GPL-3.0
- Last updated
- 2w ago
- Created
- 109mo 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
Open pull requests
No open pull requests.
Top contributors
Recent releases
Similar repos
dessant/search-by-image
Search by Image is a browser extension for reverse image search across 30+...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
|
1.6k | +3 | JavaScript | 7/10 | 2w ago |
|
|
1.5k | — | TypeScript | 7/10 | 3w ago |
|
|
27.9k | — | Python | 8/10 | 1w ago |
|
|
2.2k | — | Go | 7/10 | 5d ago |
|
|
3.6k | — | JavaScript | 7/10 | 2w ago |
|
|
1.7k | — | JavaScript | 7/10 | 24h ago |
ArchiveBox (27,851 stars, Python) is a self-hosted, full-stack archiving system for creating personal web archives. Web Archives is lightweight client-side integration with public archives. ArchiveBox is heavier, more comprehensive; Web Archives is quicker to deploy and use.
archiveweb.page (1,511 stars, TypeScript) allows users to create and browse web archives locally. Web Archives aggregates existing public archives. Both are lightweight; archiveweb.page is creator-focused, Web Archives is consumer-focused.
wabarc (2,211 stars, Go) is a command-line tool for archiving. Web Archives is GUI-centric browser extension. Different user personas and workflows; minimal direct overlap.
Users can visit archive.org directly. Web Archives reduces friction by surfacing archives without leaving the page. Utility is primarily convenience; does not replace the underlying archive.
Also by dessant (3,584 stars). Similar cross-browser extension pattern; suggests author expertise in extension distribution and UX. Web Archives follows proven design and deployment model.





