Is DevTools+ by URLflows safe?
Checked version: 0.4.0 · Scan date (UTC): 2026-11-01
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
Manage other extensions
Can enable, disable, or uninstall other browser extensions
Browser debugger access
Can attach to tabs and inspect/modify all page data using Chrome DevTools protocol
Capture screen content
Can capture screenshots or video of your screen, windows, or tabs
Execute scripts in pages
Can inject and execute JavaScript code in web pages
Access browser cookies
Can read and modify cookies, potentially accessing login sessions
Delete browsing data
Can remove browsing history, cookies, cache, and other browsing data
Store local data
Can save data locally in the browser for persistence
Access current tab
Can temporarily access the content of the active tab when you click the extension
Add context menu items
Can add custom items to the right-click context menu
Read clipboard
Can read text and data currently on your clipboard
Write to clipboard
Can place content onto your clipboard
Block network requests (declarative)
Can block or redirect network requests using predefined rules without seeing content
Create offscreen documents
Can create hidden documents for background processing tasks
CPU info
Can query CPU information
Are you the author of DevTools+ by URLflows?
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.4.0
- Current listed version
- 0.4.0
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 3 critical and 12 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.