Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_license/ee248ce48d7b6f69b6f37df42a9a78db570d5b40
commit
ee248ce48d7b6f69b6f37df42a9a78db570d5b40
[log]
author
Keith Smiley <keithbsmiley@gmail.com>
Wed Apr 29 11:12:53 2026 -0700
committer
Keith Smiley <keithbsmiley@gmail.com>
Wed Apr 29 11:13:30 2026 -0700
tree
303d4a5f553974c3e31d4d9adaf2df328d74e851
parent
a3ad07d7b111a386e1d8e0ed9bf9b592af367b99 [diff]
Fix exec config with 9.x

https://github.com/bazelbuild/bazel/issues/29421

This isn't the perfect fix but I'm not sure if we want to add a dep on
bazel_features to get the right one
1 file changed
tree: 303d4a5f553974c3e31d4d9adaf2df328d74e851
  1. .bazelci/
  2. .github/
  3. admin/
  4. distro/
  5. doc_build/
  6. docs/
  7. examples/
  8. licenses/
  9. rules/
  10. rules_gathering/
  11. sample_reports/
  12. tests/
  13. tools/
  14. .gitignore
  15. BUILD
  16. CODEOWNERS
  17. deps.bzl
  18. LICENSE
  19. MODULE.bazel
  20. README.md
  21. version.bzl
  22. WORKSPACE
  23. WORKSPACE.bzlmod
README.md

rules_license

CI: Build status

:warning: WARNING
Active development has moved to https://github.com/bazel-contrib/supply-chain. Please look there for current status. If you wish to contribute, please consider doing your work there.

This repository contains a set of rules and tools for

  • declaring metadata about packages, such as
    • the licenses the package is available under
    • the canonical package name and version
    • copyright information
    • ... and more TBD in the future
  • gathering license declarations into artifacts to ship with code
  • applying organization specific compliance constraints against the set of packages used by a target.
  • producing SBOMs for built artifacts.

Background reading:

These is for learning about the problem space, and our approach to solutions. Concrete specifications will always appear in checked in code rather than documents.