ClipBuddy - Clipboard History Manager (Fast, Secure & Reliable) extension
Security at a glance
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: hhmjebkfbebnajkiajhagmoebelndcik
Permissions (7)
- View open tabs
Related extensions
Clipboard History Manager - Secure, Fast, and Open SourceProductivity
ClipTrack - Clipboard History ManagerProductivity
Clipboard History Manager - Secure, Fast, and Open SourceTools
Clipboard Manager - Smart History ManagerTools
Smart Clipboard History ManagerTools
Smart Clipboard: History & Source TrackerTools
Frequently asked questions
Is ClipBuddy - Clipboard History Manager (Fast, Secure & Reliable) safe to use?
Our latest automated scan rates the Chrome listing of ClipBuddy - Clipboard History Manager (Fast, Secure & Reliable) at 76/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 ClipBuddy - Clipboard History Manager (Fast, Secure & Reliable) require?
ClipBuddy - Clipboard History Manager (Fast, Secure & Reliable) requests 7 permissions. The most significant: View open tabs. See the full breakdown in the security report.
Who develops ClipBuddy - Clipboard History Manager (Fast, Secure & Reliable)?
ClipBuddy - Clipboard History Manager (Fast, Secure & Reliable) is published by AddonsZone.com. 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
- 1.3.0 – HTML copy support
- Current listed version
- 1.3.0 – HTML copy support
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 1 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.