npm Trusted Publish Lint
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 credential in your release workflow that expires before your next release
Install
npm-trusted-publish-lint file
Node 18+. The same 15 rules as the VS Code extension, from a terminal or CI.
Free
- Open a workflow, .npmrc or package.json and get every npm publish credential, OIDC and provenance gap named on its own line by all 15 rules - no key, no account
--ruleslists every rule
With a licence ($29 once)
- Sweep every workflow in the repository in one pass and export the finished audit as a dated Markdown or CSV file you keep and hand to a reviewer
npm-trusted-publish-lint --dir ./templates --report html --out report.html
A freelance DevOps engineer is a median $60/hour on Upwork (typical range $40-$100); reading one release workflow and rewriting it for OIDC is most of an hour
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "npm-trusted-publish-lint": { "command": "npm-trusted-publish-lint", "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: npm Trusted Publish Lint
run: pip install rulestamp-npm-trusted-publish-lint && npm-trusted-publish-lint --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-npm-trusted-publish-lint
npm-trusted-publish-lint --help
Metadata
Release files for rulestamp-npm-trusted-publish-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 |
|---|---|---|---|---|
| rulestamp_npm_trusted_publish_lint-1.0.7.tar.gz | 16.0 kB | Without provenance | Details for rulestamp_npm_trusted_publish_lint-1.0.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_npm_trusted_publish_lint-1.0.7-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_npm_trusted_publish_lint-1.0.7-py3-none-any.whl |
Total release size: 34.2 kB
Release files / rulestamp_npm_trusted_publish_lint-1.0.7.tar.gz
| Download URL | rulestamp_npm_trusted_publish_lint-1.0.7.tar.gz |
|---|---|
| Size | 16.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d9d85e347a0f7a6e1df1dec94cf3561944dd46756127136835e914943019ce57
|
|
BLAKE2b-256 checksum How to use checksums |
d85111790b523d3e34a8a278c62db2ed68822d8dbf9a9ab80498919840b2652b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_npm_trusted_publish_lint-1.0.7-py3-none-any.whl
| Download URL | rulestamp_npm_trusted_publish_lint-1.0.7-py3-none-any.whl |
|---|---|
| Size | 18.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7550b9d7a5ff8b47bafe799285a13c3bfa3c1bf09f1045edd9b5ca17810c1cae
|
|
BLAKE2b-256 checksum How to use checksums |
b6906ac3f069cd50cf9c00a477781a5b820bb177bab1c0b731b6dc5e203fc44d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-npm-trusted-publish-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.