A project I work on imports bazel-diff transitively and fails to find license information for bazel-diff.
Most of our external dependencies which are built with Bazel have a license target (from rules_license) in the BUILD.bazel at the top of the repo.
To track licenses of external dependencies we rely on most projects using rules_license to document license information and we patch that in for dependencies that don't satisfy this requirement upstream.
Would you be interested in adding a license target to your project? Using license targets seem to to be an opportunity for Bazel built projects to achieve a common way of documenting and handling license information for external dependencies. Of course there's the issue of rules_license having moved active development over to the supply-chain project which is still in early development.
I could understand if you are hesitant to adopt license tagets from rules_license so but if you are interested I could create a pull request for it.
A project I work on imports bazel-diff transitively and fails to find license information for bazel-diff.
Most of our external dependencies which are built with Bazel have a license target (from rules_license) in the BUILD.bazel at the top of the repo.
To track licenses of external dependencies we rely on most projects using rules_license to document license information and we patch that in for dependencies that don't satisfy this requirement upstream.
Would you be interested in adding a license target to your project? Using license targets seem to to be an opportunity for Bazel built projects to achieve a common way of documenting and handling license information for external dependencies. Of course there's the issue of rules_license having moved active development over to the supply-chain project which is still in early development.
I could understand if you are hesitant to adopt license tagets from rules_license so but if you are interested I could create a pull request for it.