AI Model License Lint
Runs the same checker as the npm package
@readystack/ai-model-license-linton a Node.js runtime that pip installs for you (nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
Reads the open-weight model IDs in your code and names the licence clause that binds you - 22 rules, 17 findings on a 33-line fixture
Install
ai-model-license-lint file
Node 18+. The same 22 rules as the VS Code extension, from a terminal or CI.
Free
- Scans the file you have open and names, for every open-weight model identifier, the exact licence clause that binds you and the case that breaks it - 22 rules, in VS Code and in the browser, no account. On the bundled 33-line fixture it returns 17 findings, 5 of them blocking, naming 7 licences; on the clean fixture it returns 0.
--ruleslists every rule
With a licence ($29 once)
- Exports the evidence: a generated NOTICE / attribution file and a dated per-model obligation report for the whole workspace, in the form procurement and counsel ask for, plus a CI exit code so a new model ID cannot land unreviewed.
@readystack/ai-model-license-lint --dir ./templates --report html --out report.html
Outside technology counsel bills roughly USD 350-600 per hour for an open-source and model-licence review, repeated each time the model list changes
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "ai-model-license-lint": { "command": "npx", "args": ["-y", "@readystack/ai-model-license-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: AI Model License Lint
run: npx -y @readystack/ai-model-license-lint --dir . --ci
(container: docker run --rm -v "$PWD:/work" getreadystack/ai-model-license-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-ai-model-license-lint
ai-model-license-lint --help
Metadata
Release files for readystack-ai-model-license-lint 1.0.7.post1
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_ai_model_license_lint-1.0.7.post1.tar.gz | 18.0 kB | Without provenance | Details for readystack_ai_model_license_lint-1.0.7.post1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| readystack_ai_model_license_lint-1.0.7.post1-py3-none-any.whl | Python 3 | none | any | Details for readystack_ai_model_license_lint-1.0.7.post1-py3-none-any.whl |
Total release size: 38.1 kB
Release files / readystack_ai_model_license_lint-1.0.7.post1.tar.gz
| Download URL | readystack_ai_model_license_lint-1.0.7.post1.tar.gz |
|---|---|
| Size | 18.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5136d0d07cc2d5d37c4f7d81ffc928a0b5a2eea9b880b2445ad7c57775b50dfa
|
|
BLAKE2b-256 checksum How to use checksums |
042a228ebf6736cd58388ef966821654cda7af0f158ee0c826b0b90527ad413f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / readystack_ai_model_license_lint-1.0.7.post1-py3-none-any.whl
| Download URL | readystack_ai_model_license_lint-1.0.7.post1-py3-none-any.whl |
|---|---|
| Size | 20.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
81462f90f0736f4878f92f830dc6512c47c3636ddd06755f3255dbb0dd142b3b
|
|
BLAKE2b-256 checksum How to use checksums |
06450a55fb089f28f08210d9e81431ddaa0dbc23fa3d0259b0a1f16218ff24cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for readystack-ai-model-license-lint 1.0.7.post1
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.