Big Clipboard - Clipboard Manager & Clipboard History extension
Security at a glance
Describes the Chrome listing; other stores are scanned separately and can score differently. Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.
See the full security reportChrome listing ID: ebcbicnmiahafaebbllibmpgneocaaih
Permissions (10)
- View open tabs
- Execute scripts in pages
Related extensions
Clipboard History – Best Clipboard Manager for ChromeProductivity
Clipboard History Manager - Your Clipboard, OrganizedProductivity
Copy History +: The Best Clipboard History Manager ToolProductivity
Clipboard History ManagerProductivity
Multi-Clipboard — Clipboard History Manager & Copy Paste HistoryProductivity
Big Clipboard - Clipboard Manager & Clipboard HistoryProductivity
Frequently asked questions
Is Big Clipboard - Clipboard Manager & Clipboard History safe to use?
Our latest automated scan rates the Chrome listing of Big Clipboard - Clipboard Manager & Clipboard History at 81/100 (some risk) — malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.
What permissions does Big Clipboard - Clipboard Manager & Clipboard History require?
Big Clipboard - Clipboard Manager & Clipboard History requests 10 permissions. The most significant: View open tabs, Execute scripts in pages. See the full breakdown in the security report.
Who develops Big Clipboard - Clipboard Manager & Clipboard History?
Big Clipboard - Clipboard Manager & Clipboard History is published by gravyware. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.
What this assessment covers
- Store listing
- Chrome
- Checked version
- 3.3.0
- Current listed version
- 3.3.0
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 2 critical and 3 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.
Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisher’s servers. A low-risk result is not a guarantee of safety. How our checks work.