PrintFriendly: Print, PDF Editor & Full Page Screenshot 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: ohlencieiipommannpdfcmfdpjjmeolj
Permissions (10)
- Execute scripts in pages
- Access browser cookies
- Manage downloads
Related extensions
Frequently asked questions
Is PrintFriendly: Print, PDF Editor & Full Page Screenshot safe to use?
Our latest automated scan rates the Chrome listing of PrintFriendly: Print, PDF Editor & Full Page Screenshot at 62/100 (elevated 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 PrintFriendly: Print, PDF Editor & Full Page Screenshot require?
PrintFriendly: Print, PDF Editor & Full Page Screenshot requests 10 permissions. The most significant: Execute scripts in pages, Access browser cookies, Manage downloads. See the full breakdown in the security report.
Who develops PrintFriendly: Print, PDF Editor & Full Page Screenshot?
PrintFriendly: Print, PDF Editor & Full Page Screenshot is published by PrintFriendly. 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
- 6.9.5
- Current listed version
- 7.4.0
- Scan date (UTC)
- Assessment status
- Completed
The current store version differs from the checked package. These results describe version 6.9.5; they do not verify version 7.4.0.
Recorded findings: 0 critical and 11 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.