Opt-Out Signal Lint for US State Privacy Laws
Runs the same checker as the npm package
@readystack/optout-signal-linton a Node.js runtime that pip installs for you (nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
Finds the ad and analytics code that keeps firing after a visitor’s browser has already sent Global Privacy Control.
Install
optout-signal-lint file
Node 18+. The same 20 rules as the VS Code extension, from a terminal or CI.
Free
- Audits the file you have open — every line against all 20 rules, no key, no limit, no sign-up.
--ruleslists every rule
With a licence ($29 once)
- Sweeps the whole workspace, writes the finding list to CSV, JSON or HTML, and returns a CI exit code so the same leak cannot merge twice.
@readystack/optout-signal-lint --dir ./templates --report html --out report.html
Osano, the nearest hosted consent platform, starts at $199/month.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "optout-signal-lint": { "command": "npx", "args": ["-y", "@readystack/optout-signal-lint", "--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.
Use in CI
- name: Opt-Out Signal Lint for US State Privacy Laws
run: npx -y @readystack/optout-signal-lint --dir . --ci
(container: docker run --rm -v "$PWD:/work" getreadystack/optout-signal-lint --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-optout-signal-lint
optout-signal-lint --help
Metadata
Release files for readystack-optout-signal-lint 0.1.7
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_optout_signal_lint-0.1.7.tar.gz | 14.7 kB | Without provenance | Details for readystack_optout_signal_lint-0.1.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| readystack_optout_signal_lint-0.1.7-py3-none-any.whl | Python 3 | none | any | Details for readystack_optout_signal_lint-0.1.7-py3-none-any.whl |
Total release size: 31.1 kB
Release files / readystack_optout_signal_lint-0.1.7.tar.gz
| Download URL | readystack_optout_signal_lint-0.1.7.tar.gz |
|---|---|
| Size | 14.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fd53027d313f0830bb9f8a570b7f55fd793a2042a58b1c4f58958078d09d0d0a
|
|
BLAKE2b-256 checksum How to use checksums |
3eb0b30638f86cb3168c42c9b2802c3d8f1c24868d9e2d667769d5a62b1176be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / readystack_optout_signal_lint-0.1.7-py3-none-any.whl
| Download URL | readystack_optout_signal_lint-0.1.7-py3-none-any.whl |
|---|---|
| Size | 16.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9e4a7ab4f7624ad6d8cfcff45bec4c1c3b3add98d4ff41d0ff6abe3288ce27a4
|
|
BLAKE2b-256 checksum How to use checksums |
26bdeef914bcef24e79f919411932f68b354247654821138413f8fb8328b4f1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for readystack-optout-signal-lint 0.1.7
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.