Refresh Watcher: Auto Refresh and 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: nghkchdkpainfgfbjnjbnjepmmepbgjf
Permissions (7)
- Execute scripts in pages
Related extensions
AutoRefresher | Auto Refresh boosting Page MonitorProductivity
AutoRefreshPage – Tab Refresh & Page MonitorProductivity
RefreshWatch – Auto Refresh & Page MonitorProductivity
Auto Refresh & Change Alert - RefreshWatchProductivity
Refresh Watch: Auto Refresh & Change AlertsProductivity
Refresh & Watch: auto refresh + change alertProductivity
Frequently asked questions
Is Refresh Watcher: Auto Refresh and Page Change Alerts safe to use?
Our latest automated scan rates the Chrome listing of Refresh Watcher: Auto Refresh and Page Change Alerts at 78/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 Refresh Watcher: Auto Refresh and Page Change Alerts require?
Refresh Watcher: Auto Refresh and Page Change Alerts requests 7 permissions. The most significant: Execute scripts in pages. See the full breakdown in the security report.
Who develops Refresh Watcher: Auto Refresh and Page Change Alerts?
Refresh Watcher: Auto Refresh and Page Change Alerts is published by om@ray.vin. 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
- 0.1.1
- Current listed version
- 0.1.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.