JDK 25 Upgrade Blocker Lint
Finds the Java lines the new LTS removed — 18 rules; 23 findings in one 64-line fixture
Install
jdk25-upgrade-blocker-lint file
Node 18+. The same 18 rules as the VS Code extension, from a terminal or CI.
Free
- Lints the .java file you have open with all 18 rules, no key and no cap — the bundled 64-line fixture returns 23 findings, 15 errors and 8 warnings; the fixed copy returns 0.
--ruleslists every rule
With a licence ($29 once)
- Sweeps the whole workspace and writes the dated migration report file — every file, blocker, JEP and replacement — for the upgrade ticket; free for the first 7 days, then one key, commercial and CI-seat use included.
@readystack/jdk25-upgrade-blocker-lint --dir ./templates --report html --out report.html
A Java migration consultant bills $120-$200 an hour; a two-day audit of one repo is over $2,000.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "jdk25-upgrade-blocker-lint": { "command": "npx", "args": ["-y", "@readystack/jdk25-upgrade-blocker-lint", "--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.
Use in CI
- name: JDK 25 Upgrade Blocker Lint
run: npx -y @readystack/jdk25-upgrade-blocker-lint --dir . --ci
(container: docker run --rm -v "$PWD:/work" getreadystack/jdk25-upgrade-blocker-lint --dir /work --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 readystack-jdk25-upgrade-blocker-lint
jdk25-upgrade-blocker-lint --help
Metadata
Release files for readystack-jdk25-upgrade-blocker-lint 1.0.4.post1
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 |
|---|---|---|---|---|
| readystack_jdk25_upgrade_blocker_lint-1.0.4.post1.tar.gz | 12.4 kB | Without provenance | Details for readystack_jdk25_upgrade_blocker_lint-1.0.4.post1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| readystack_jdk25_upgrade_blocker_lint-1.0.4.post1-py3-none-any.whl | Python 3 | none | any | Details for readystack_jdk25_upgrade_blocker_lint-1.0.4.post1-py3-none-any.whl |
Total release size: 26.5 kB
Release files / readystack_jdk25_upgrade_blocker_lint-1.0.4.post1.tar.gz
| Download URL | readystack_jdk25_upgrade_blocker_lint-1.0.4.post1.tar.gz |
|---|---|
| Size | 12.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3bec36647e013fa87b76923399a88b84462f4f1c15d9f50b0d27dadf13c16655
|
|
BLAKE2b-256 checksum How to use checksums |
6ddb93461a973e6fe88950862ed21f9fbf2548f98dfa093a800da05ae44cf6a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / readystack_jdk25_upgrade_blocker_lint-1.0.4.post1-py3-none-any.whl
| Download URL | readystack_jdk25_upgrade_blocker_lint-1.0.4.post1-py3-none-any.whl |
|---|---|
| Size | 14.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1ac4b9e7d826ed2e931009de166d19553b1f4ff52d2347ec3437b40ca7365c90
|
|
BLAKE2b-256 checksum How to use checksums |
b9df2ad1b6fd715167f7f9e583bb58d00b9828104f5718c2cecd2d6da83e66f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for readystack-jdk25-upgrade-blocker-lint 1.0.4.post1
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.