インボイス経過措置リンター 2026(80%→70%)
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.
2026年9月30日で80%控除が終わります。10月1日からは50%ではなく70%です(令和8年度税制改正)。請求・仕入コードに残った 0.8 と 0.5、明細ごとの端数処理、T+13桁でない登録番号を、行番号と修正案つきで指摘します。
Install
jct-transition-lint-2026 file
Node 18+. The same 24 rules as the VS Code extension, from a terminal or CI.
Free
- 請求・仕入の計算コードを1ファイル貼るか開くだけで、24規則すべてを当てて、行番号・深刻度・修正案つきの指摘を全部そのまま出します。件数を隠したり、ぼかしたり、途中で止めたりしません。コードは端末から出ません。
--ruleslists every rule
With a licence ($29 once)
- 1ファイルではなくリポジトリ全体を走査し、指摘一覧を CSV/JSON/HTML に書き出し、保存のたびに再検査し、CI が読む JSON を出します。2026年10月1日以降に 0.8 が戻ってくるのを、プルリクで機械が止めます。
jct-transition-lint-2026 --dir ./templates --report html --out report.html
税理士のスポット相談は1時間5,000〜15,000円、高度な税務判断を伴う相談では10,000〜30,000円が相場です。
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "jct-transition-lint-2026": { "command": "jct-transition-lint-2026", "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: インボイス経過措置リンター 2026(80%→70%)
run: pip install rulestamp-jct-transition-lint-2026 && jct-transition-lint-2026 --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-jct-transition-lint-2026
jct-transition-lint-2026 --help
Metadata
Release files for rulestamp-jct-transition-lint-2026 0.1.8
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_jct_transition_lint_2026-0.1.8.tar.gz | 16.2 kB | Without provenance | Details for rulestamp_jct_transition_lint_2026-0.1.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_jct_transition_lint_2026-0.1.8-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_jct_transition_lint_2026-0.1.8-py3-none-any.whl |
Total release size: 33.9 kB
Release files / rulestamp_jct_transition_lint_2026-0.1.8.tar.gz
| Download URL | rulestamp_jct_transition_lint_2026-0.1.8.tar.gz |
|---|---|
| Size | 16.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4632847efd5d6c393e200d0f3482f0650104d7d7b1dcd3649b4ffd798424c86f
|
|
BLAKE2b-256 checksum How to use checksums |
9d53ea493ced79656fb90ec390a2d70cda8739b5f770963b1909949119e69e75
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_jct_transition_lint_2026-0.1.8-py3-none-any.whl
| Download URL | rulestamp_jct_transition_lint_2026-0.1.8-py3-none-any.whl |
|---|---|
| Size | 17.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
be3142e23e3bfc5784f93bfb268c50a666ececc8409b95a2acb6dc1b9ed466ab
|
|
BLAKE2b-256 checksum How to use checksums |
2bbeb95564e82cb550e56310501ce094cc14a198ed1ea3b9ffcb0a35c4200841
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-jct-transition-lint-2026 0.1.8
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.