Stale Standard Citation 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 standards and laws your reStructuredText or Markdown docs still cite after they died, and the date each one died; 44 rules, 30 findings in the 57-line sample page
Install
stale-standard-citation-lint file
Node 18+. The same 44 rules as the VS Code extension, from a terminal or CI.
Free
- Check the document open in the editor (or pasted into the web page) and name every dead citation in it, with the date it died and what replaced it
--ruleslists every rule
With a licence ($29 once)
- Sweep every .rst/.md/.txt in the workspace and write a dated STALE-CITATIONS.md report, file by file, that you can hand an auditor or attach to a security questionnaire
stale-standard-citation-lint --dir ./templates --report html --out report.html
GRC consultants bill $150-$300 an hour to read compliance documentation; a single page review is rarely under an hour
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "stale-standard-citation-lint": { "command": "stale-standard-citation-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: Stale Standard Citation Lint
run: pip install rulestamp-stale-standard-citation-lint && stale-standard-citation-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-stale-standard-citation-lint
stale-standard-citation-lint --help
Metadata
Release files for rulestamp-stale-standard-citation-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_stale_standard_citation_lint-1.0.7.tar.gz | 18.9 kB | Without provenance | Details for rulestamp_stale_standard_citation_lint-1.0.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_stale_standard_citation_lint-1.0.7-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_stale_standard_citation_lint-1.0.7-py3-none-any.whl |
Total release size: 40.0 kB
Release files / rulestamp_stale_standard_citation_lint-1.0.7.tar.gz
| Download URL | rulestamp_stale_standard_citation_lint-1.0.7.tar.gz |
|---|---|
| Size | 18.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
146acbaaf28f23564902096b2277b80ca4ad754ad92b1b60f047ba3a5266a145
|
|
BLAKE2b-256 checksum How to use checksums |
bad3133341830fe83ac09e0ef982499a1dea44507b643e05d943e10473a7b9fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_stale_standard_citation_lint-1.0.7-py3-none-any.whl
| Download URL | rulestamp_stale_standard_citation_lint-1.0.7-py3-none-any.whl |
|---|---|
| Size | 21.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
85048b6072d38ddce62808b50702a1e5f3c71a2fe93765a5d84e38c74bb86938
|
|
BLAKE2b-256 checksum How to use checksums |
3197410483c6e9d6f5753a46fcb022625856b724c2af8041d391768c2ae120ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-stale-standard-citation-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.