Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_license / 677149517c5b56dcccefe6dced03273f1c991b63
commit677149517c5b56dcccefe6dced03273f1c991b63[log] [tgz]
authorTony Aiuto <aiuto>Thu Jul 10 09:23:03 2025 -0400
committerTony Aiuto <aiuto>Thu Jul 10 09:23:03 2025 -0400
treec3dc8b576f4f9d0d5ef50dbe01e9b6ee14bd7d67
parented72667d37259b63d58b0d0757d4fadc4035d206 [diff]
damm markdown
1 file changed
tree: c3dc8b576f4f9d0d5ef50dbe01e9b6ee14bd7d67
  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.