Extension security retrospective & comparison
Why choose TabBoy after the lessons of The Great Suspender
In 2021, The Great Suspender (installed by millions of users) was secretly transferred to an unknown entity, injected with malicious tracking scripts (v7.1.8+), and subsequently banned by Google as malware. This incident demonstrated the profound risk of opaque extensions injecting scripts into open tabs. TabBoy is built on radical security: 100% open source (MIT), zero network permissions, no external server communication, and structured collection management that never tampers with your active webpage DOM.
Zero-Network Architecture
TabBoy requests no network permissions and has no backend servers. It cannot phone home, exfiltrate URLs, or load remote scripts.
100% Verifiable Open Source
Every line of code is public and MIT-licensed on GitHub. Changes are tracked openly in public pull requests with automated security checks.
Non-Invasive Tab Control
TabBoy organizes tabs through standard browser tabs APIs and never injects content scripts, proxy frames, or tracking payloads into your browsing sessions.
Chrome Native Memory Synergy
Instead of risky script-based tab hijacking, TabBoy complements Chrome's native Memory Saver (Chrome 108+) to keep your computer fast and safe.
TabBoy vs The Great Suspender: Security & Architecture Matrix
A point-by-point retrospective on extension safety, supply chain integrity, and tab management models.
| Security Criterion / Architecture | TabBoy | The Great Suspender (Legacy) |
|---|---|---|
| Network Access & Permissions | 0 network calls (Zero-network manifest policy) | Requested broad network access (injected tracking servers in v7.1.8) |
| Chrome Web Store Status | Verified & Compliant MV3 Extension | Removed & Banned by Google as malware (Feb 2021) |
| Source Code Transparency | 100% Open Source on GitHub (MIT License) | Secretly transferred ownership to anonymous entity (2020) |
| Content Script Injection | No content scripts injected into web pages | Replaced web page DOM with custom extension URLs |
| Tab Loss & Corrupted URLs | Zero risk (Standard URLs preserved in local collections) | High risk (Orphaned chrome-extension:// URLs upon removal) |
| Memory Management Method | Structured collection archiving + Chrome native memory discard | Custom script-based suspension & tab hijacking |
| Automated Rule Organization | Deterministic JSON rules, regex & domain routing | Timer-based inactivity suspension only |
| Multi-Window & Tab Groups | Preserves native tab groups, colors, and window order | Ungrouped flat suspended tabs |
| Markdown & PKM Export | 1-Click Obsidian & Notion formatted Markdown export | No structured markdown export |
| Explicit Action Confirmation | Always required with automatic safety snapshots | Automatic background tab closing/suspending |
When to choose native memory freezing rather than TabBoy
Understanding the difference between memory discarding and persistent tab organization.
Automated In-Memory Tab Discarding
If you strictly want automated discarding of inactive background tabs from RAM, enable Chrome's built-in Memory Saver (chrome://settings/performance) which achieves this natively without any extension security risks.
Timer-Based Inactivity Suspension
If your workflow depends strictly on an automated timer that unloads tabs after N minutes of inactivity rather than actively categorizing work into structured collections.
How to safely recover tabs and move to TabBoy
Restore corrupted suspended URLs and organize your tabs with verifiable security.
Recover any orphaned suspended URLs
If you have leftover tabs stuck with 'chrome-extension://...uri=https://example.com', extract the original web address from the query parameter or restore from browser history.
Import tabs into TabBoy collections
Open TabBoy Collections and organize your open tabs into structured spaces with automatic snapshots and rule sorting.
Enable Chrome native Memory Saver
In Chrome Settings -> Performance, enable 'Memory Saver' to let Chrome discard inactive tabs natively without third-party extension vulnerabilities.
Official & verified sources
- Google Chrome Web Store Security Policy on Malware & Deceptive Software(August 2026): Documentation on extension ban policies and remote code execution restrictions under MV3.
- The Great Suspender Incident Archive & Community Security Audit(August 2026): Technical retrospective of the v7.1.8 ownership transfer, tracking payload injection, and CVE analysis.
- Chrome Performance & Memory Saver Architecture Guide(August 2026): Native browser tab discarding specifications (tabs.discard API).
Other Competitor Comparisons
TabBoy vs Session Buddy
The classic session saver vs automated local tab intelligence & safe v4 alternative
Read full comparisonTabBoy vs Workona
Cloud team workspace manager vs local-first privacy & unlimited spaces
Read full comparisonTabBoy vs OneTab
Flat RAM dumping vs non-destructive tab organization & safety snapshots
Read full comparisonTabBoy vs Toby
Visual card bookmarking vs unlimited local tab automation
Read full comparisonSwitch to safe, verifiable tab organization
Protect your browsing security with TabBoy: zero-network architecture, 100% open source, and local privacy.