Screenshot — Full Page Capture, Region & Annotate | ShotFrame 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: odbehkkgpadgeamcajjdlllppnoioakl
Permissions (5)
- Execute scripts in pages
- Manage downloads
Related extensions
Full Page Screenshot — Capture & AnnotateProductivity
FullPage Screenshot – Capture, Annotate, Blur & Record Clips (No Login)Productivity
Full Page Screenshot & Screen CaptureProductivity
Screenshot, Annotate & Redact - ShotKeepProductivity
PageShot - Full Page ScreenshotProductivity
Full Page Screenshot & EditorProductivity
Frequently asked questions
Is Screenshot — Full Page Capture, Region & Annotate | ShotFrame safe to use?
Our latest automated scan rates the Chrome listing of Screenshot — Full Page Capture, Region & Annotate | ShotFrame at 84/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 Screenshot — Full Page Capture, Region & Annotate | ShotFrame require?
Screenshot — Full Page Capture, Region & Annotate | ShotFrame requests 5 permissions. The most significant: Execute scripts in pages, Manage downloads. See the full breakdown in the security report.
Who develops Screenshot — Full Page Capture, Region & Annotate | ShotFrame?
Screenshot — Full Page Capture, Region & Annotate | ShotFrame is published by MIE. 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.0
- Current listed version
- 1.0.0
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 critical and 1 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.