XSLT Fix: XSLT Polyfill, XML Viewer & XSLT Tester extension

Security at a glance

Some riskSafety score 66/10071 findings

Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.

See the full security report

Chrome listing ID: mnjaeijlilgdpmfnkkfbehobkdcmkhne

Permissions (6)

  • Execute scripts in pages

Frequently asked questions

Is XSLT Fix: XSLT Polyfill, XML Viewer & XSLT Tester safe to use?

Our latest automated scan rates the Chrome listing of XSLT Fix: XSLT Polyfill, XML Viewer & XSLT Tester at 66/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 Fix: XSLT Polyfill, XML Viewer & XSLT Tester require?

XSLT Fix: XSLT Polyfill, XML Viewer & XSLT Tester requests 6 permissions. The most significant: Execute scripts in pages. See the full breakdown in the security report.

Who develops XSLT Fix: XSLT Polyfill, XML Viewer & XSLT Tester?

XSLT Fix: XSLT Polyfill, XML Viewer & XSLT Tester is published by meetdevrim@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.4.1
Current listed version
1.4.1
Scan date (UTC)
Assessment status
Completed

Recorded findings: 3 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.

Compare extensions by task