(I'd be happy to author the PR for this if you're open to this change! I'm happy to set it up any way you want. One possible idea is a new top level folder called bundles with the latest minor version of each major version of reuse-tool below it, e.g. /bundles/reuse-v5.py and /bundles/reuse-v5.py)

As good as reuse-tool is, please don't loose sight of the fact it's practically non-essential for all software projects—which have been doing fine without reuse-tool for 30+ years. That is to say, I and a lot of other people won't integrate reuse-tool into our projects if it adds any complexity or any hassle anywhere. Software complexity is an ugly bitch and nobody wants their build system or dev tools to be more hassle than is necessary.

Making reuse-tool only available via pip / pipx is a non-starter complexity-wise for most-every non-python project and is turning away many potential adopters of reuse-tool. At the same time, it's very reasonable to expect python to be installed on any computer building software in any language as its so ubiquitous throughout all manner of build systems—even the Linux kernel!

In short, I propose a single-python-file bundled distribution option for downloading reuse-tool locally so that adopters don't have to wrangle trying to reconcile their build system and dev tools with pip / pipx. E.g. pinliner is a great tool for bundling python into single-file distributions. This will significantly expedite widespread adoption of reuse-tool.