Google Git
Sign in
fuchsia / third_party / github.com / bazelbuild / rules_license / 796d237aaffbb690aaf44f5aa962f50578b485b7
commit796d237aaffbb690aaf44f5aa962f50578b485b7[log] [tgz]
authoraiuto <aiuto@google.com>Fri May 19 12:15:10 2023 -0400
committerGitHub <noreply@github.com>Fri May 19 12:15:10 2023 -0400
treea2b7317239ba39708e8bba9806b9d3742bfe047f
parentcfbf25b6aa192a721753d624c50c85f22793317c [diff]
parentfb628b4e9071e24ab3e3ccc68fe4b43be4fbfb75 [diff]
Merge pull request #95 from aiuto/longname

fix handling of long-name
tree: a2b7317239ba39708e8bba9806b9d3742bfe047f
  1. .bazelci/
  2. .github/
  3. admin/
  4. distro/
  5. doc_build/
  6. docs/
  7. examples/
  8. licenses/
  9. rules/
  10. rules_gathering/
  11. tests/
  12. tools/
  13. .gitignore
  14. BUILD
  15. CODEOWNERS
  16. deps.bzl
  17. LICENSE
  18. MODULE.bazel
  19. README.md
  20. version.bzl
  21. WORKSPACE
  22. 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.