.NET EOL & CRA Support Window Gate
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 target framework in a .csproj against Microsoft's end-of-support day and against the support period you promise
Install
dotnet-eol-support-gate file
Node 18+. The same 10 rules as the VS Code extension, from a terminal or CI.
Free
- Dates one .csproj, Directory.Build.props or global.json you have open: every target framework, SDK pin and runtime-bound package gets its real end-of-support date, the days left, and the months it falls short of the support period you promise. 10 checks, no key.
--ruleslists every rule
With a licence ($29 once)
- Runs the same dating over every project file in the workspace in one pass and writes the dated support-window evidence file you keep and hand to an auditor.
dotnet-eol-support-gate --dir ./templates --report html --out report.html
Having a contractor inventory runtime support dates across a solution and write the evidence page is commonly quoted as a multi-day engagement
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "dotnet-eol-support-gate": { "command": "dotnet-eol-support-gate", "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: .NET EOL & CRA Support Window Gate
run: pip install rulestamp-dotnet-eol-support-gate && dotnet-eol-support-gate --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-dotnet-eol-support-gate
dotnet-eol-support-gate --help
Metadata
Release files for rulestamp-dotnet-eol-support-gate 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_dotnet_eol_support_gate-1.0.7.tar.gz | 16.8 kB | Without provenance | Details for rulestamp_dotnet_eol_support_gate-1.0.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_dotnet_eol_support_gate-1.0.7-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_dotnet_eol_support_gate-1.0.7-py3-none-any.whl |
Total release size: 36.2 kB
Release files / rulestamp_dotnet_eol_support_gate-1.0.7.tar.gz
| Download URL | rulestamp_dotnet_eol_support_gate-1.0.7.tar.gz |
|---|---|
| Size | 16.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eff64c2d9797dd3a5fb70eb4a6276f7672defb5dd7a3f007d1fc20c899690f46
|
|
BLAKE2b-256 checksum How to use checksums |
dcae21af92b08299201ea6ada53d17ad67b58318205d260c63b5cb497ec33987
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_dotnet_eol_support_gate-1.0.7-py3-none-any.whl
| Download URL | rulestamp_dotnet_eol_support_gate-1.0.7-py3-none-any.whl |
|---|---|
| Size | 19.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
03223901721619921b71d764857ae15194f3d3de425a252373126039cef18e08
|
|
BLAKE2b-256 checksum How to use checksums |
d5dde8dbf48f930f24215ad90aedecd0523960bc0999cf2108503b824325de26
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-dotnet-eol-support-gate 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.