PQC Deprecation Lint — RSA/ECC after 2030
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.
Dates every quantum-vulnerable algorithm in your code against the NIST IR 8547 clock: deprecated after 2030-12-31, disallowed after 2035-12-31.
Install
pqc-deprecation-lint file
Node 18+. The same 17 rules as the VS Code extension, from a terminal or CI.
Free
- Check the file open in the editor and see every quantum-vulnerable algorithm in it, with line numbers and each one dated against the NIST IR 8547 clock for a date you choose
--ruleslists every rule
With a licence ($29 once)
- Sweep the whole workspace in one pass and write a dated migration report file you keep — the artifact for a customer security questionnaire, a migration ticket, or next quarter's diff
pqc-deprecation-lint --dir ./templates --report html --out report.html
A security consultant doing the same cryptographic inventory by hand bills $150-$250 an hour, and the first pass over one repository is a day
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "pqc-deprecation-lint": { "command": "pqc-deprecation-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: PQC Deprecation Lint — RSA/ECC after 2030
run: pip install rulestamp-pqc-deprecation-lint && pqc-deprecation-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-pqc-deprecation-lint
pqc-deprecation-lint --help
Metadata
Release files for rulestamp-pqc-deprecation-lint 1.0.8
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_pqc_deprecation_lint-1.0.8.tar.gz | 18.0 kB | Without provenance | Details for rulestamp_pqc_deprecation_lint-1.0.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_pqc_deprecation_lint-1.0.8-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_pqc_deprecation_lint-1.0.8-py3-none-any.whl |
Total release size: 38.2 kB
Release files / rulestamp_pqc_deprecation_lint-1.0.8.tar.gz
| Download URL | rulestamp_pqc_deprecation_lint-1.0.8.tar.gz |
|---|---|
| Size | 18.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0294546da07677d56083761f36563d5f2a02b024589fe55ec3792abf2fe4a03f
|
|
BLAKE2b-256 checksum How to use checksums |
f63c543dba2fbd32eda285d8901ee1b9d6f86b3027795b0f5de673c336bea16c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_pqc_deprecation_lint-1.0.8-py3-none-any.whl
| Download URL | rulestamp_pqc_deprecation_lint-1.0.8-py3-none-any.whl |
|---|---|
| Size | 20.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b0f292859855426cd9b80f4f31449b600acba0e617b3eb32dd46f214060f42e2
|
|
BLAKE2b-256 checksum How to use checksums |
83d54262b493f0283f0ee673f08ba6a0446cb87972a85e5c3634e6871ed7999c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-pqc-deprecation-lint 1.0.8
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.