vsix-publish-lint
io.github.jmshinhwa/vsix-publish-lint
Find the package.json lines that stop vsce before you run the release build
Description as published in the official MCP registry.
What we measured
| Endpoint | None listed (runs locally) | registry |
|---|---|---|
| GitHub stars | 0 | github.com/jmshinhwa/readystack-themes |
| Last push | 2026-10-03 | GitHub API |
| Registry version | 1.0.4 · active · updated 2026-09-19 | registry |
| Package | npm: @readystack/vsix-publish-lint | registry |
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows a real call went through, not just an opinion. How to file one.
Connect
npx -y @readystack/vsix-publish-lintCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- npm-trusted-publish-lint Finds the credential in your release workflow that expires before your next release
- Lulu Ads — Publisher Concierge Self-serve publisher onboarding for Lulu Ads. 70% CPA, disclosed sponsored field.
- RTBlint Validate OpenRTB bid requests and responses against IAB specs. ARTF, Rust core.
- Bluesky Keyword Alerts Search bounded public Bluesky keywords, handles, mentions, and hashtags.
- RSS Keyword Monitor Search bounded RSS, Atom, and RDF feed matches by keyword or regex.
- TED Tender Monitor Search EU TED procurement notices by CPV, country, keyword, value, or type.
Badge for your README
Shows the result of our latest check and links back to this page.
[](https://openforallofus.com/tools/io.github.jmshinhwa/vsix-publish-lint)Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name io.github.jmshinhwa/vsix-publish-lint.