VSIX Publish Lint
Runs the same checker as the npm package
@readystack/vsix-publish-linton a Node.js runtime that pip installs for you (nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
Find the package.json lines that stop vsce before you run the release build
Install
vsix-publish-lint file
Node 18+. The same 16 rules as the VS Code extension, from a terminal or CI.
Free
- Lints the extension manifest you have open against all 16 rules and names, line by line, the exact field to change
--ruleslists every rule
With a licence ($29 once)
- Lints every extension manifest in the workspace in one pass and writes the result out as a JSON or SARIF file you keep and run in CI
@readystack/vsix-publish-lint --dir ./templates --report html --out report.html
One hour of specialised freelance developer time runs $75-$150 on Upwork's own 2026 rate guide; a rejected publish usually costs more than one.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "vsix-publish-lint": { "command": "npx", "args": ["-y", "@readystack/vsix-publish-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: VSIX Publish Lint
run: npx -y @readystack/vsix-publish-lint --dir . --ci
(container: docker run --rm -v "$PWD:/work" getreadystack/vsix-publish-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-vsix-publish-lint
vsix-publish-lint --help
Metadata
Release files for readystack-vsix-publish-lint 1.0.10.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_vsix_publish_lint-1.0.10.post1.tar.gz | 17.4 kB | Without provenance | Details for readystack_vsix_publish_lint-1.0.10.post1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| readystack_vsix_publish_lint-1.0.10.post1-py3-none-any.whl | Python 3 | none | any | Details for readystack_vsix_publish_lint-1.0.10.post1-py3-none-any.whl |
Total release size: 36.9 kB
Release files / readystack_vsix_publish_lint-1.0.10.post1.tar.gz
| Download URL | readystack_vsix_publish_lint-1.0.10.post1.tar.gz |
|---|---|
| Size | 17.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6897242aa3a0c10f65c914337aac6d134b0b4a62d9491cda73377864b5af79c2
|
|
BLAKE2b-256 checksum How to use checksums |
e4bbcdffd8c8f451e606b5f28f61f1bbb05b6e0b5860b309658b49ca6cb9927f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / readystack_vsix_publish_lint-1.0.10.post1-py3-none-any.whl
| Download URL | readystack_vsix_publish_lint-1.0.10.post1-py3-none-any.whl |
|---|---|
| Size | 19.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
92f4bd85c265381265eec7daa955bf2848885f9cede5a102d60da4f43da47a1c
|
|
BLAKE2b-256 checksum How to use checksums |
eae5776b7647fc282e3151cfa3c3d597b5d06a45516c400b4e2dd581a3e2d83d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for readystack-vsix-publish-lint 1.0.10.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.