Google Git
Sign in
android/platform/external/bazelbuild-rules_license/refs/tags/android-14.0.0_r26
tag
5ecd410d7be5376541b048bd0520fbf51e57f8aa
tagger
The Android Open Source Project <initial-contribution@android.com>
Mon Feb 05 11:36:55 2024 -0800
object
50a220cc046640f32b067a0f8aee427606fdf13e
Android 14.0.0 Release 26 (UQ1A.240205.004.A1)
commit
50a220cc046640f32b067a0f8aee427606fdf13e
[log]
author
Jingwen Chen <jingwen@google.com>
Sat Mar 25 07:49:02 2023 +0000
committer
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Sat Mar 25 07:49:02 2023 +0000
tree
39314478665e3c080e3df6fe4a97609182f089b5
parent
8a99d2b6dff36f04be445f3c5e8f69874da57a04 [diff]
parent
0f22c081a0b9df29e574400ebf7003014b04a06d [diff]
Merge remote-tracking branch 'aosp/upstream-main' into mymerge am: 748e62d604 am: dad1665d12 am: eb146bbc49 am: 0f22c081a0

Original change: https://android-review.googlesource.com/c/platform/external/bazelbuild-rules_license/+/2500461

Change-Id: Ia4417578b69e463bda18867fef6a3815971f3b3a
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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.