Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_license / 25728a44161475c91e69052d9a813f0d02814840
commit25728a44161475c91e69052d9a813f0d02814840[log] [tgz]
authorTony Aiuto <aiuto>Wed Jul 09 23:33:08 2025 -0400
committerTony Aiuto <aiuto>Wed Jul 09 23:33:08 2025 -0400
treee574d79b092c0e57ac4133cc51c0ae1800299499
parent5b980eaa19dec16c85d8ec5e58c16257c8738ea3 [diff]
Update doc to point to bazel-contrib/supply-chain
1 file changed
tree: e574d79b092c0e57ac4133cc51c0ae1800299499
  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

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.

NOTE: 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.

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.