Google Git
Sign in
android / platform / external / bazelbuild-rules_license / 989ccbf8d64556d248b10d8797951bd03a9ea326
commit989ccbf8d64556d248b10d8797951bd03a9ea326[log] [tgz]
authoraiuto <aiuto@google.com>Fri Dec 16 13:10:13 2022 -0500
committerGitHub <noreply@github.com>Fri Dec 16 13:10:13 2022 -0500
tree84e6c5bdd765d3a42e86b7d74c4aebc01ddcd091
parent7a977d270f554114784c1eec7a5ef0f5aa92be02 [diff]
parent50a911beef394976c061a3066304fef256f64be9 [diff]
Merge pull request #66 from aiuto/doc2

Add missing docs glue.  This usually takes several iterations just to turn on. None of this is executable, or part of the distribution builds, so I am force submitting.
tree: 84e6c5bdd765d3a42e86b7d74c4aebc01ddcd091
  1. .bazelci/
  2. .github/
  3. admin/
  4. distro/
  5. docs/
  6. examples/
  7. licenses/
  8. rules/
  9. tests/
  10. tools/
  11. .gitignore
  12. BUILD
  13. CODEOWNERS
  14. deps.bzl
  15. LICENSE
  16. MODULE.bazel
  17. README.md
  18. version.bzl
  19. WORKSPACE
  20. 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.