Google Git
Sign in
fuchsia / third_party / github.com / bazelbuild / rules_license / refs/tags/0.0.7
commite160ce519a3ab82d407bc57a0f0b0510d61a3a59[log] [tgz]
authoraiuto <aiuto@google.com>Fri Jun 16 17:01:42 2023 -0400
committerGitHub <noreply@github.com>Fri Jun 16 17:01:42 2023 -0400
tree2489429b4e21cd325062dc80dc3cc8917e84961a
parentc3f8a8b40cc362da12c18de6150c12f18dcde2dc [diff]
parent42ed8a91a864b6ede3c02e0de0f90cdac7d6ccdd [diff]
Merge pull request #105 from aiuto/rtest

Add a super-hackey smoke test for distributions.
tree: 2489429b4e21cd325062dc80dc3cc8917e84961a
  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.