AI Companion Safety 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.
Reads your companion chatbot's system prompt against California SB 243, New York GBL Article 47, Illinois HB 1806 (WOPR Act) and Nevada AB 406, line by line.
Install
ai-companion-safety-lint file
Node 18+. The same 14 rules as the VS Code extension, from a terminal or CI.
Free
- Scan every prompt, persona and character-card file in the workspace and see each SB 243 / NY Art. 47 duty the text breaks or never states, with the line number and the statute section.
--ruleslists every rule
With a licence ($29 once)
- Export the dated evidence pack - every file, finding, statute section and rule-set version in one Markdown/JSON artifact you keep, diff between releases and hand to an app-store reviewer or to counsel.
ai-companion-safety-lint --dir ./templates --report html --out report.html
Outside privacy counsel reviews prompt text at roughly $400 an hour
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "ai-companion-safety-lint": { "command": "ai-companion-safety-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: AI Companion Safety Lint
run: pip install rulestamp-ai-companion-safety-lint && ai-companion-safety-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-ai-companion-safety-lint
ai-companion-safety-lint --help
Metadata
Release files for rulestamp-ai-companion-safety-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_ai_companion_safety_lint-1.0.7.tar.gz | 16.6 kB | Without provenance | Details for rulestamp_ai_companion_safety_lint-1.0.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_ai_companion_safety_lint-1.0.7-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_ai_companion_safety_lint-1.0.7-py3-none-any.whl |
Total release size: 35.4 kB
Release files / rulestamp_ai_companion_safety_lint-1.0.7.tar.gz
| Download URL | rulestamp_ai_companion_safety_lint-1.0.7.tar.gz |
|---|---|
| Size | 16.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b12d4fbbffe6bc683a723f3fba8996ca0162b484086be1b52fd2983b13249880
|
|
BLAKE2b-256 checksum How to use checksums |
cb31c871c13480446dbed099c235f996a6b91da9c9ef37db505960f494edafde
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_ai_companion_safety_lint-1.0.7-py3-none-any.whl
| Download URL | rulestamp_ai_companion_safety_lint-1.0.7-py3-none-any.whl |
|---|---|
| Size | 18.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
81c3b073facc13439ead653de7132f3e88780f6202174118fbec099b9d3b8dfb
|
|
BLAKE2b-256 checksum How to use checksums |
27acc0497f505bf1c575694a17874bb5edd78f0404c98fe39d17bf1a14f4426e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-ai-companion-safety-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.