Google GitGoogle Git
Sign in
pigweed/third_party/github/bazelbuild/rules_license/4f29d54b29241d9d7c66faec7776210e21dec881
commit
4f29d54b29241d9d7c66faec7776210e21dec881
[log]
author
Tony Aiuto <tony.aiuto@datadoghq.com>
Fri Dec 19 22:07:08 2025 -0500
committer
Tony Aiuto <tony.aiuto@datadoghq.com>
Fri Dec 19 22:07:08 2025 -0500
tree
89846fd1a8d09241c77aef27d20f40274b1303c8
parent
f27beb61ec306f5466941a1a993249281d05e4be [diff]
clean up some things that break with bazel 10
1 file changed
tree: 89846fd1a8d09241c77aef27d20f40274b1303c8
  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.