Google Git
Sign in
android / platform / external / bazelbuild-rules_license / 748e62d604243251488beae40ccc754f998c11bb
commit748e62d604243251488beae40ccc754f998c11bb[log] [tgz]
authorJingwen Chen <jingwen@google.com>Wed Mar 22 07:01:37 2023 +0000
committerJingwen Chen <jingwen@google.com>Wed Mar 22 07:33:01 2023 +0000
tree39314478665e3c080e3df6fe4a97609182f089b5
parentdf3b8d7aa1d57f6ee108a023e90860f1e372cb4b [diff]
parentbb6f02d8ce7e51587e600671d41e801960d16bf1 [diff]
Merge remote-tracking branch 'aosp/upstream-main' into mymerge

Also add METADATA file.

Test: presubmits

Change-Id: I39e818bebf11430b15efa915b5c48e717a590096
tree: 39314478665e3c080e3df6fe4a97609182f089b5
  1. .bazelci/
  2. .github/
  3. admin/
  4. distro/
  5. doc_build/
  6. docs/
  7. examples/
  8. licenses/
  9. rules/
  10. tests/
  11. tools/
  12. .gitignore
  13. BUILD
  14. CODEOWNERS
  15. deps.bzl
  16. LICENSE
  17. METADATA
  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.