Is PXS for Developers safe?
Checked version: 0.2.7 · Scan date (UTC): 2026-10-25
Automated analysis of publicly available code — not a professional security audit. It may produce false positives and does not prove an extension is unsafe or safe. Treat it as one signal among many. Disclaimer · Report an issue
How it ranks
Findings breakdown
detected
Permissions requested
Browser debugger access
Can attach to tabs and inspect/modify all page data using Chrome DevTools protocol
Execute scripts in pages
Can inject and execute JavaScript code in web pages
Manage downloads
Can initiate downloads and access your download history
Capture tab content
Can capture audio and video streams from browser tabs
Access browser cookies(optional)
Can read and modify cookies, potentially accessing login sessions
Access current tab
Can temporarily access the content of the active tab when you click the extension
Store local data
Can save data locally in the browser for persistence
Write to clipboard
Can place content onto your clipboard
Are you the author of PXS for Developers?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
What this assessment covers
- Store listing
- Chrome
- Checked version
- 0.2.7
- Current listed version
- 0.2.7
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 3 critical and 4 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.