waigdt extension

Security at a glance

Some riskSafety score 84/10029 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: ldfnkkjjnjojfeibnkphcocmacannecn

Permissions (1)

  • Store local data

Frequently asked questions

Is waigdt safe to use?

Our latest automated scan rates the Chrome listing of waigdt at 84/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 waigdt require?

waigdt requests 1 permission. The most significant: Store local data. See the full breakdown in the security report.

Who develops waigdt?

waigdt is published by mustansir.dev. 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
Current listed version
1.0
Scan date (UTC)
Assessment status
Completed

Recorded findings: 1 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