TabVigil: Auto Refresh & Page Change Alerts 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: fmnecjbohpajpiibhfcgkjcabacnmnnb
Permissions (6)
- Execute scripts in pages
Related extensions
Auto Refresh Ultra: Tab Reloader & Page MonitorProductivity
Auto RefreshProductivity
Tab Reload Timer — Auto Refresh PagesProductivity
Auto Refresh Page, Tab Reloader & Page Monitor - Auto Reload Tabs and PagesProductivity
Auto Refresh: Tab Reloader, Page Monitor & Price AlertsProductivity
Auto Refresh & Change Alert - RefreshWatchProductivity
Frequently asked questions
Is TabVigil: Auto Refresh & Page Change Alerts safe to use?
Our latest automated scan rates the Chrome listing of TabVigil: Auto Refresh & Page Change Alerts at 85/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 TabVigil: Auto Refresh & Page Change Alerts require?
TabVigil: Auto Refresh & Page Change Alerts requests 6 permissions. The most significant: Execute scripts in pages. See the full breakdown in the security report.
Who develops TabVigil: Auto Refresh & Page Change Alerts?
TabVigil: Auto Refresh & Page Change Alerts is published by lockespop@gmail.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.0.1
- Current listed version
- 1.0.1
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 2 critical and 2 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.