License Flip Audit - BUSL/SSPL/AGPL in your deps
Runs the same checker as our npm package on a Node.js runtime that pip installs for you (
nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
Finds the dependencies whose licence changed under you - Terraform 1.6+ BUSL, Redis 7.4+ SSPL, Bitnami's August 2025 move, Elastic 7.11 - and names the exact version where each flip happened.
Install
license-flip-audit file
Node 18+. The same 30 rules as the VS Code extension, from a terminal or CI.
Free
- Checks the manifest you have open end to end - every line, all 30 recorded flips, full findings, no watermark and no trial.
--ruleslists every rule
With a licence ($29 once)
- Scans every manifest in the workspace, exports the CSV/JSON/HTML report a security review asks for, re-checks on every save, and writes a JSON file CI can fail a pull request on.
license-flip-audit --dir ./templates --report html --out report.html
The Bitnami flip alone pushed teams onto a Bitnami Secure subscription reported at $50,000-$72,000 a year.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "license-flip-audit": { "command": "license-flip-audit", "args": ["--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.
Use in CI
- name: License Flip Audit - BUSL/SSPL/AGPL in your deps
run: pip install rulestamp-license-flip-audit && license-flip-audit --dir . --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 rulestamp-license-flip-audit
license-flip-audit --help
Metadata
Release files for rulestamp-license-flip-audit 0.1.8
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 |
|---|---|---|---|---|
| rulestamp_license_flip_audit-0.1.8.tar.gz | 15.3 kB | Without provenance | Details for rulestamp_license_flip_audit-0.1.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_license_flip_audit-0.1.8-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_license_flip_audit-0.1.8-py3-none-any.whl |
Total release size: 32.3 kB
Release files / rulestamp_license_flip_audit-0.1.8.tar.gz
| Download URL | rulestamp_license_flip_audit-0.1.8.tar.gz |
|---|---|
| Size | 15.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1a49144010adde6a14135a1871d09d3f20821e30b3a9731f37dbadaf67056284
|
|
BLAKE2b-256 checksum How to use checksums |
bdaa3a9818cbb1794fa1eccc67ba25de6d357e68e65b231d7753ef815105b4b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_license_flip_audit-0.1.8-py3-none-any.whl
| Download URL | rulestamp_license_flip_audit-0.1.8-py3-none-any.whl |
|---|---|
| Size | 17.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bd2c848a49485fa90f09a072ac55ceee33db01dfc8846d5bc8e1a61f1beddeb0
|
|
BLAKE2b-256 checksum How to use checksums |
32cb2019ceec3b5479ae67baabc70ad972818bef0c331d714432cebd7e5fbc5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-license-flip-audit 0.1.8
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.