Google GitGoogle Git
Sign in
pigweed/third_party/github/bazelbuild/rules_license/ab73ff2bc1853f9aa87db066c53e19af9da13b3e
commit
ab73ff2bc1853f9aa87db066c53e19af9da13b3e
[log]
author
aiuto <aiuto@google.com>
Wed Jun 14 11:23:04 2023 -0400
committer
GitHub <noreply@github.com>
Wed Jun 14 11:23:04 2023 -0400
tree
71cce2a823dd8f6a4f2cccf48ce1d3c330195d5e
parent
d2d24ea73637cba00e875d9b37c560d2218cf42e [diff]
parent
fd5464135dffe2728624c6cf3792e3ee1ee9b33e [diff]
Merge pull request #101 from aiuto/bfr

Move rules/private/gathering_providers.bzl to rules_gathering
tree: 71cce2a823dd8f6a4f2cccf48ce1d3c330195d5e
  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.