GitHub Better LaTeX extension

Security at a glance

Some riskSafety score 83/10041 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: pgjmlgekphjkjcpdmcglchomjhionpdf

Permissions

GitHub Better LaTeX requests no special permissions.

Frequently asked questions

Is GitHub Better LaTeX safe to use?

Our latest automated scan rates the Chrome listing of GitHub Better LaTeX at 83/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 GitHub Better LaTeX require?

GitHub Better LaTeX requests no special permissions according to its latest store listing.

Who develops GitHub Better LaTeX?

GitHub Better LaTeX is published by Seunghoon Lee. 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.1.1
Current listed version
0.1.1
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.

Compare extensions by task