Processing boundary
Input is processed only in the active browser tab's memory and is not sent to a ByteQuant server.
52
Code & file security
Code Security Pre-Scan
Scans code in a time-bounded Web Worker with explainable regex rules and reports eval, innerHTML, shell commands, SQL concatenation, weak hashes, and possible secrets with line numbers. It cannot understand full builds or data flow and does not replace SAST or expert review.
✓ Free✓ No account✓ In-browser
Result
Your result will appear here.
Persistent storage
Input and output are not stored. The optional usage counter keeps only tool identity and count, never content.
Verification
Output comes from disclosed rules or browser APIs and needs independent review before high-impact use.
A result in three steps
- 01
Paste only source code you are authorized to inspect.
- 02
Choose a language and run the local time-bounded scan.
- 03
Verify each finding against data flow and context; rotate exposed secrets immediately.
When is this tool useful?
- ✓ Pull-request pre-checks
- ✓ Secret discovery in snippets
- ✓ Preparing for security review
Important limitation
Automated output is a preliminary assessment. Do not use it alone for legal, financial, medical, or security-critical decisions.
LEARN THE WORKFLOW
Guides for this tool
How to Combine Code Security Pre-Scans, SAST, and Manual Review
Turn fast regex findings into a sound security workflow with data-flow analysis, dependency checks, SAST, and expert review.
Read guide →PWA Installation and Offline Caching: A Privacy-First Design Guide
Understand web app installation, the service worker lifecycle, and cache boundaries that keep sensitive inputs out of persistent storage.
Read guide →ABOUT THIS TOOL
Frequently asked questions
Does this tool send input to a server?+
No. Processing runs in this browser tab. Data leaves the page only when you choose to copy or download the result.
Is the result definitive?+
The tool produces consistent output from disclosed rules and browser APIs, but context, data quality, and method limitations can affect it. Verify high-impact decisions.
Is input saved?+
No. Tool input is not persisted. With consent, only tool identity and usage count may be kept on this device for personal shortcuts.