Google Git
Sign in
fuchsia / third_party / github.com / bazelbuild / rules_license / refs/tags/0.0.4
commite3bdc544ef373156da36638b774d65ff2d978bfa[log] [tgz]
authoraiuto <aiuto@google.com>Wed Nov 02 00:20:00 2022 -0400
committerGitHub <noreply@github.com>Wed Nov 02 00:20:00 2022 -0400
tree4ed49f7c5737ed0cece8039f6185a0e4a6b74a9c
parent3b80554a610916e34d2cda79f77f0eb35a5c7b84 [diff]
parent3e56c48e13b0d77d181170b1ea67d6b52486cf11 [diff]
Merge pull request #53 from aiuto/from_piper

Mega merge of improvements from Google
tree: 4ed49f7c5737ed0cece8039f6185a0e4a6b74a9c
  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. README.md
  17. version.bzl
  18. WORKSPACE
README.md

rules_license

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.