Refresh & Watch: auto refresh + change alert 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: ameebaoilldcdfdackaeohcnmmgfmllf
Permissions (6)
- Execute scripts in pages
Related extensions
SmartRefresh – Auto Refresh & Page MonitorProductivity
Auto Refresh — Page Monitor & ReloadProductivity
Auto Refresh — Page Monitor & ReloadProductivity
Auto Refresh: Tab Reloader, Page Monitor & Price AlertsProductivity
Auto Refresh & Change Alert - RefreshWatchProductivity
Refresh Watch: Auto Refresh & Change AlertsProductivity
Frequently asked questions
Is Refresh & Watch: auto refresh + change alert safe to use?
Our latest automated scan rates the Chrome listing of Refresh & Watch: auto refresh + change alert 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 & Watch: auto refresh + change alert require?
Refresh & Watch: auto refresh + change alert requests 6 permissions. The most significant: Execute scripts in pages. See the full breakdown in the security report.
Who develops Refresh & Watch: auto refresh + change alert?
Refresh & Watch: auto refresh + change alert is published by sergey.gubyonov@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
- 0.3.0
- Current listed version
- 0.3.0
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 1 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.