SVG Asset Compliance Lint
Runs the same checker as the npm package
@readystack/svg-asset-compliance-linton a Node.js runtime that pip installs for you (nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
14 rules over the SVG files your design tool exported, before they become a legal object
Install
svg-asset-compliance-lint file
Node 18+. The same 14 rules as the VS Code extension, from a terminal or CI.
Free
- Check the SVG open in the editor, or pasted into the free web page, against all 14 rules — that file is finished, no key, no limit.
--ruleslists every rule
With a licence ($29 once)
- Sweep every SVG in the workspace in one command and write a dated conformity report file you own and can hand to an auditor (scope + ownership).
@readystack/svg-asset-compliance-lint --dir ./templates --report html --out report.html
A manual accessibility audit of a component library is quoted in the thousands of dollars; a front-end developer opening 300 exported icons one at a time is the alternative.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "svg-asset-compliance-lint": { "command": "npx", "args": ["-y", "@readystack/svg-asset-compliance-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: SVG Asset Compliance Lint
run: npx -y @readystack/svg-asset-compliance-lint --dir . --ci
(container: docker run --rm -v "$PWD:/work" getreadystack/svg-asset-compliance-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-svg-asset-compliance-lint
svg-asset-compliance-lint --help
Metadata
Release files for readystack-svg-asset-compliance-lint 1.0.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_svg_asset_compliance_lint-1.0.7.tar.gz | 17.8 kB | Without provenance | Details for readystack_svg_asset_compliance_lint-1.0.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| readystack_svg_asset_compliance_lint-1.0.7-py3-none-any.whl | Python 3 | none | any | Details for readystack_svg_asset_compliance_lint-1.0.7-py3-none-any.whl |
Total release size: 37.8 kB
Release files / readystack_svg_asset_compliance_lint-1.0.7.tar.gz
| Download URL | readystack_svg_asset_compliance_lint-1.0.7.tar.gz |
|---|---|
| Size | 17.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ff56b532c877663ead84b61e6c7d63ab3fc6f7e2e5e04abe76c6957865f7e892
|
|
BLAKE2b-256 checksum How to use checksums |
b2a113c528e4d119df3502abb02fa2168d69cfc735d225caf8c7b2b10d40f63d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / readystack_svg_asset_compliance_lint-1.0.7-py3-none-any.whl
| Download URL | readystack_svg_asset_compliance_lint-1.0.7-py3-none-any.whl |
|---|---|
| Size | 20.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fb2f9435f253bedc5081ed3bcf1a81c0dea4b04285aa1b11dbe6950151d6c133
|
|
BLAKE2b-256 checksum How to use checksums |
cc355be82d9291828261c328bb16b8c25747f8a7b43433ee620be762b057a6ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for readystack-svg-asset-compliance-lint 1.0.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.