Farm Loss Notice Lint: Crop Insurance Deadlines
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.
Crop insurance claim form deadlines from 7 CFR 457.8 section 14: notice within 72 hours of discovering damage, no later than 15 days after the insurance period ends, phone notice confirmed in writing within 15 days, prevented planting notice within 72 hours after the final planting date, claim within 60 days after the insurance period ends.
Install
farm-loss-notice-lint file
Node 18+. The same 9 rules as the VS Code extension, from a terminal or CI.
Free
- Checks the loss log open in the editor against every 7 CFR 457.8 section 14 notice and claim deadline and prints each missed date.
--ruleslists every rule
With a licence ($29 once)
- Scan every unit log in the workspace at once and export a CSV deadline report per unit for the agency file.
farm-loss-notice-lint --dir ./templates --report html --out report.html
Under 7 CFR 457.8 section 14(b)(5), a missed notice of loss makes the loss uninsured: no indemnity is paid and premiums are still owed.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "farm-loss-notice-lint": { "command": "farm-loss-notice-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: Farm Loss Notice Lint: Crop Insurance Deadlines
run: pip install rulestamp-farm-loss-notice-lint && farm-loss-notice-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-farm-loss-notice-lint
farm-loss-notice-lint --help
Metadata
Release files for rulestamp-farm-loss-notice-lint 1.0.1
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_farm_loss_notice_lint-1.0.1.tar.gz | 16.1 kB | Without provenance | Details for rulestamp_farm_loss_notice_lint-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_farm_loss_notice_lint-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_farm_loss_notice_lint-1.0.1-py3-none-any.whl |
Total release size: 34.5 kB
Release files / rulestamp_farm_loss_notice_lint-1.0.1.tar.gz
| Download URL | rulestamp_farm_loss_notice_lint-1.0.1.tar.gz |
|---|---|
| Size | 16.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
15d20b4871123dcdc0bb4217baf15839a588907613deba3f0e528ae83bcad63a
|
|
BLAKE2b-256 checksum How to use checksums |
0d1ecfd88b7148c24d317175d3b39124d7d083563626546b244ab57fcd395224
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_farm_loss_notice_lint-1.0.1-py3-none-any.whl
| Download URL | rulestamp_farm_loss_notice_lint-1.0.1-py3-none-any.whl |
|---|---|
| Size | 18.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4375c93c6504217a11e217de351a41c0068b8283f09dfebe4f271c56b5075d00
|
|
BLAKE2b-256 checksum How to use checksums |
dd0c8b4206bf498c33900dd8c874e6e832912e7f1a7e47eb17084de8b3ac3515
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-farm-loss-notice-lint 1.0.1
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.