Tracepaper: Pixel Perfect Overlay, Ruler, Color Picker & CSS Inspector 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: hfflamlbhlhdgigmioabjhgpbcmghdfl
Permissions (4)
- Execute scripts in pages
Related extensions
ScreenRulerProductivity
LayerGuide: Pixel Perfect Overlay, Ruler, Guides & InspectorProductivity
Design X-Ray — CSS Inspector, Spacing Ruler & Color PickerProductivity
Page Measure – Pixel Ruler, Spacing & Color PickerProductivity
OverlayPeek — overlay, inspect, live CSSProductivity
Tracing Paper: Pixel Perfect OverlayProductivity
Frequently asked questions
Is Tracepaper: Pixel Perfect Overlay, Ruler, Color Picker & CSS Inspector safe to use?
Our latest automated scan rates the Chrome listing of Tracepaper: Pixel Perfect Overlay, Ruler, Color Picker & CSS Inspector at 88/100 (low 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 Tracepaper: Pixel Perfect Overlay, Ruler, Color Picker & CSS Inspector require?
Tracepaper: Pixel Perfect Overlay, Ruler, Color Picker & CSS Inspector requests 4 permissions. The most significant: Execute scripts in pages. See the full breakdown in the security report.
Who develops Tracepaper: Pixel Perfect Overlay, Ruler, Color Picker & CSS Inspector?
Tracepaper: Pixel Perfect Overlay, Ruler, Color Picker & CSS Inspector is published by DecisionsCalc. 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.4.0
- Current listed version
- 0.4.0
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 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.