1# rules_license 2 3CI: [](https://buildkite.com/bazel/rules-license) 4 5This repository contains a set of rules and tools for 6- declaring metadata about packages, such as 7 - the licenses the package is available under 8 - the canonical package name and version 9 - copyright information 10 - ... and more TBD in the future 11- gathering those license declarations into artifacts to ship with code 12- applying organization specific compliance constriants against the 13 set of packages used by a target. 14- (eventually) producing SBOMs for built artifacts. 15 16WARNING: The code here is still in active initial development and will churn a lot. 17 18If you want to follow along: 19- Mailing list: [[email protected]](https://groups.google.com/a/bazel.build/g/bazel-ssc) 20- Monthly eng meeting: [calendar link](MjAyMjA4MjJUMTYwMDAwWiBjXzUzcHBwZzFudWthZXRmb3E5NzhxaXViNmxzQGc&tmsrc=c_53pppg1nukaetfoq978qiub6ls%40group.calendar.google.com&scp=ALL) 21- [Latest docs](https://bazelbuild.github.io/rules_license/latest.html) 22 23Background reading: 24These is for learning about the problem space, and our approach to solutions. Concrete specifications will always appear in checked in code rather than documents. 25- [License Checking with Bazel](https://docs.google.com/document/d/1uwBuhAoBNrw8tmFs-NxlssI6VRolidGYdYqagLqHWt8/edit#). 26- [OSS Licenses and Bazel Dependency Management](https://docs.google.com/document/d/1oY53dQ0pOPEbEvIvQ3TvHcFKClkimlF9AtN89EPiVJU/edit#) 27- [Adding OSS license declarations to Bazel](https://docs.google.com/document/d/1XszGbpMYNHk_FGRxKJ9IXW10KxMPdQpF5wWbZFpA4C8/edit#heading=h.5mcn15i0e1ch) 28
){kind=link}