Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_license/f83a73e15add76fa1747de4fbbc055f39a4a0614
commit
f83a73e15add76fa1747de4fbbc055f39a4a0614
[log]
author
Tony Aiuto <aiuto@google.com>
Thu Oct 19 14:35:44 2023 -0400
committer
Tony Aiuto <aiuto@google.com>
Thu Oct 19 14:35:44 2023 -0400
tree
e62a98ef98ddabafb5752937123aeb64334458de
parent
7806287cd576c8ddf8b09e5db5cb88c3f1510ea9 [diff]
parent
39d9f429b563478e1c16fb0f938d178ccf4c3fd3 [diff]
Merge remote-tracking branch 'upstream/main'
tree: e62a98ef98ddabafb5752937123aeb64334458de
  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 those license declarations into artifacts to ship with code
  • applying organization specific compliance constriants against the set of packages used by a target.
  • (eventually) producing SBOMs for built artifacts.

WARNING: The code here is still in active initial development and will churn a lot.

If you want to follow along:

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.