XSLT Polyfill - XML to HTML Viewer & XSLTProcessor 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: chfldcedcadmbbplaehbejnoenohdicn
Permissions (6)
- Execute scripts in pages
Related extensions
XSLT PolyfillMake Chrome Yours
XSLT PolyfillOther
XSLT Browser Support - XSLT Polyfill, XML Viewer & TesterMake Chrome Yours
XSLT Prism - XSLT Polyfill, XML Viewer & XSLT TesterMake Chrome Yours
XMLNest – XML Viewer & XSLT PolyfillMake Chrome Yours
XSLT Fix: XSLT Polyfill, XML Viewer & XSLT TesterDeveloper
Frequently asked questions
Is XSLT Polyfill - XML to HTML Viewer & XSLTProcessor safe to use?
Our latest automated scan rates the Chrome listing of XSLT Polyfill - XML to HTML Viewer & XSLTProcessor at 70/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 XSLT Polyfill - XML to HTML Viewer & XSLTProcessor require?
XSLT Polyfill - XML to HTML Viewer & XSLTProcessor requests 6 permissions. The most significant: Execute scripts in pages. See the full breakdown in the security report.
Who develops XSLT Polyfill - XML to HTML Viewer & XSLTProcessor?
XSLT Polyfill - XML to HTML Viewer & XSLTProcessor is published by pnumberorg@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
- 1.0.1
- Current listed version
- 1.0.1
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 2 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.