galaxy-tool-lint
The advisory check tier (tier 3.5) of the Galaxy tool refactoring framework: read-only IUC best-practice checks that report but never mutate.
Where the codemod (tier 2) and fmt (tier 3) tiers fix a tool (their detect
phases report what their fix would change), this tier covers the
IUC tool_xml best-practices that are not safely auto-fixable — they
need a content or semantic decision (add tests, declare requirements, write
help). Each check is a RuleMeta-coded, detect_only=True rule that yields the
shared tier-0.5 Violation. The findings are advisory: the
galaxy-tool-refactor check command shows them but, by default, does not fail on
them (use --strict to gate on them too).
Scope
Depends only on tier 1 (galaxy-tool-source, the parsed ToolDocument and
profile helpers) and tier 0.5 (galaxy-tool-refactor-rules, RuleMeta /
Violation). It does not depend on the mutating tiers — the app
(galaxy-tool-refactor-cli) composes this alongside them.
from galaxy_tool_source.binding import load_tool
from galaxy_tool_lint.detect import detect_violations
for violation in detect_violations(load_tool("my_tool.xml")):
print(violation.code, violation.message)
Checks
See galaxy_tool_lint.checks and the IUC coverage map at
../docs/iuc_best_practices.md. GTR020.2 (single-quote Cheetah $var) is
implemented — it reads <command> text through the read-only command_text.py
lexer (quote/directive-aware, across newlines; the lexer lives in tier 1,
galaxy_tool_source.command_text, so the GTR020.1 codemod shares it) and reports one
advisory per fully-unquoted shell-line $var. Its provable subset is now
auto-fixed by the GTR020.1 codemod (docs/decisions.md D8). GTR089.2
(HelpRstResidual) is the advisory half of the GTR089 partition: it reports the
invalid <help> reStructuredText the GTR089.1 repair codemod can't safely fix,
through the same tier-1 predicate (galaxy_tool_source.rst; docs/decisions.md
D31). GTR032 (&&-vs-lone-&) is a real detector since docs/decisions.md
D34 (the data-backed D3 deferral ended when the CT3 lexer landed): the
lone_amp.py classifier flags only genuine command-joining lone &s.
Metadata
Release files for galaxy-tool-lint 0.3.9
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 |
|---|---|---|---|---|
| galaxy_tool_lint-0.3.9.tar.gz | 107.2 kB | With provenance | Details for galaxy_tool_lint-0.3.9.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| galaxy_tool_lint-0.3.9-py3-none-any.whl | Python 3 | none | any | Details for galaxy_tool_lint-0.3.9-py3-none-any.whl |
Total release size: 177.2 kB
Release files / galaxy_tool_lint-0.3.9.tar.gz
| Download URL | galaxy_tool_lint-0.3.9.tar.gz |
|---|---|
| Size | 107.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f660f47ba2a94395fb5e9f7277d9e2897f3fcee725a533d084597607c32b27a2
|
|
BLAKE2b-256 checksum How to use checksums |
0e8d516712be5c7009f271cd00f1497000f892a3d9c2c6691a066a47ec2ae21f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 5, 2026.
Transparency logRelease files / galaxy_tool_lint-0.3.9-py3-none-any.whl
| Download URL | galaxy_tool_lint-0.3.9-py3-none-any.whl |
|---|---|
| Size | 70.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d1a7b9b662d3c4f78419b5dc05f6b9a2746058245747cb46d137c7778f2850f2
|
|
BLAKE2b-256 checksum How to use checksums |
050d848bf3217268bf2cffc33c26b6be05ed70e3421a2ee70effc1b202859134
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 5, 2026.
Transparency logSecurity for galaxy-tool-lint 0.3.9
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for galaxy_tool_lint-0.3.9.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 5, 2026.
Transparency logA 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.