CallerPlugins for Teamleader Focus – Click to Call & Message 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: mdlfppdlbakkbgekpcjhcadfdkjmfaeg
Permissions (3)
- Execute scripts in pages
Related extensions
Click-to-Call for Web and CRMProductivity
CallerPlugins for Pipedrive – Click to Call & MessageProductivity
Fonable Click-to-Call: Browser Phone DialerProductivity
Call on TeamsMake Chrome Yours
CallerPlugins for HubSpot – Click to Call & MessageProductivity
CallerPlugins for Odoo – Click to Call & MessageProductivity
Frequently asked questions
Is CallerPlugins for Teamleader Focus – Click to Call & Message safe to use?
Our latest automated scan rates the Chrome listing of CallerPlugins for Teamleader Focus – Click to Call & Message at 92/100 (low 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 CallerPlugins for Teamleader Focus – Click to Call & Message require?
CallerPlugins for Teamleader Focus – Click to Call & Message requests 3 permissions. The most significant: Execute scripts in pages. See the full breakdown in the security report.
Who develops CallerPlugins for Teamleader Focus – Click to Call & Message?
CallerPlugins for Teamleader Focus – Click to Call & Message is published by svstigter. 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.0.3
- Current listed version
- 1.0.3
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 critical and 0 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.