BugScribe: Bug Reporter for QA & Developers 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: afjaaigabappebloalngbmfcfbajmcfj
Permissions (4)
- Browser debugger access
- Execute scripts in pages
Related extensions
Frequently asked questions
Is BugScribe: Bug Reporter for QA & Developers safe to use?
Our latest automated scan rates the Chrome listing of BugScribe: Bug Reporter for QA & Developers at 82/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 BugScribe: Bug Reporter for QA & Developers require?
BugScribe: Bug Reporter for QA & Developers requests 4 permissions. The most significant: Browser debugger access, Execute scripts in pages. See the full breakdown in the security report.
Who develops BugScribe: Bug Reporter for QA & Developers?
BugScribe: Bug Reporter for QA & Developers is published by Wasif Raza. 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.1.0
- Current listed version
- 1.1.0
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 1 critical and 1 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.