FramedShot: Full Page Screenshot, Annotate & Blur extension
Security at a glance
Describes the Chrome listing; other stores are scanned separately and can score differently. 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: ojodikaampkjmcldckbcgfohhcaaohhe
Permissions (6)
- Execute scripts in pages
- Capture tab content
Related extensions
FullPageSnap - Screenshot & AnnotatorDeveloper
FullPage Screenshot – Capture, Annotate, Blur & Record Clips (No Login)Productivity
Stillframe – Full Page Screenshot & EditorProductivity
FramedShot: Full Page Screenshot, Annotate & BlurSocial & Communication
Screenshot — Full Page Capture, Region & Annotate | ShotFrameProductivity
Full Page Screenshot - Full Screen Capture & EditorProductivity
Frequently asked questions
Is FramedShot: Full Page Screenshot, Annotate & Blur safe to use?
Our latest automated scan rates the Chrome listing of FramedShot: Full Page Screenshot, Annotate & Blur 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 FramedShot: Full Page Screenshot, Annotate & Blur require?
FramedShot: Full Page Screenshot, Annotate & Blur requests 6 permissions. The most significant: Execute scripts in pages, Capture tab content. See the full breakdown in the security report.
Who develops FramedShot: Full Page Screenshot, Annotate & Blur?
FramedShot: Full Page Screenshot, Annotate & Blur is published by AndreiProjects. 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
- 3.3.6
- Current listed version
- 3.3.6
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 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.