Google Git
Sign in
fuchsia / third_party / github.com / bazelbuild / rules_license / 7de72c96421484ad4d7c068fa58a68d57ea33fa1
commit7de72c96421484ad4d7c068fa58a68d57ea33fa1[log] [tgz]
authorTony Aiuto <aiuto@google.com>Mon Feb 27 15:33:12 2023 -0500
committerTony Aiuto <aiuto@google.com>Mon Feb 27 15:33:12 2023 -0500
tree2aab214566e0c086577edbf21450ca09975f78fd
parent95f66cf97ece85cfadbb4b63e6afa8cf0735a9e0 [diff]
Make rules/private a distinct package.

That allows for better visibility control.
9 files changed
tree: 2aab214566e0c086577edbf21450ca09975f78fd
  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. MODULE.bazel
  18. README.md
  19. version.bzl
  20. WORKSPACE
  21. 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.