View in Browser — Publish Leak Audit (HTML)
Runs the same checker as the npm package
@readystack/view-in-browser-leak-auditon a Node.js runtime that pip installs for you (nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
24 rules read the .html file you are about to open in the browser and flag every line that behaves differently once the page has a public URL: live API keys, localhost and file:// paths, http:// resources, a leftover noindex.
Install
view-in-browser-leak-audit file
Node 18+. The same 24 rules as the VS Code extension, from a terminal or CI.
Free
- Audit the HTML file you are about to open in the browser: all 24 rules, every finding with its severity, line number and fix. The clean fixture returns 0 findings, the dirty one returns 27. No key, no watermark, no locked answers.
--ruleslists every rule
With a licence ($29 once)
- Scope: one command sweeps every HTML file in the workspace instead of the one in front of you, and writes a dated LEAK-AUDIT.md you keep as evidence — forty pages in one pass instead of forty passes.
@readystack/view-in-browser-leak-audit --dir ./templates --report html --out report.html
In February 2026 a developer reported an $82,000 Google Cloud bill after a key embedded in client-side Google Maps code was taken from the page source; their normal spend was $180 a month.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "view-in-browser-leak-audit": { "command": "npx", "args": ["-y", "@readystack/view-in-browser-leak-audit", "--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.
Use in CI
- name: View in Browser — Publish Leak Audit (HTML)
run: npx -y @readystack/view-in-browser-leak-audit --dir . --ci
(container: docker run --rm -v "$PWD:/work" getreadystack/view-in-browser-leak-audit --dir /work --ci)
The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Install (PyPI)
pip install readystack-view-in-browser-leak-audit
view-in-browser-leak-audit --help
Metadata
Release files for readystack-view-in-browser-leak-audit 1.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| readystack_view_in_browser_leak_audit-1.0.2.tar.gz | 16.9 kB | Without provenance | Details for readystack_view_in_browser_leak_audit-1.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| readystack_view_in_browser_leak_audit-1.0.2-py3-none-any.whl | Python 3 | none | any | Details for readystack_view_in_browser_leak_audit-1.0.2-py3-none-any.whl |
Total release size: 36.0 kB
Release files / readystack_view_in_browser_leak_audit-1.0.2.tar.gz
| Download URL | readystack_view_in_browser_leak_audit-1.0.2.tar.gz |
|---|---|
| Size | 16.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6be28f9b66aef2c77da4820d695669e75e671a9234e0ec9cd7df6801722f296a
|
|
BLAKE2b-256 checksum How to use checksums |
01d2a730d1f52e37e3a5bab85b93f5ce5816cbcc7e712124777362db4155b5b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / readystack_view_in_browser_leak_audit-1.0.2-py3-none-any.whl
| Download URL | readystack_view_in_browser_leak_audit-1.0.2-py3-none-any.whl |
|---|---|
| Size | 19.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7b81a9effb0dd887fe2b436c5483bb97ad6bcd29aa956fadb1c2928959daf6f1
|
|
BLAKE2b-256 checksum How to use checksums |
08ac106af6c1360913047cfa7da16d5da1972dfb3d1945482f939b8ab7d52f3e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for readystack-view-in-browser-leak-audit 1.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.