Name Date Size #Lines LOC

..--

.bazelci/H25-Apr-2025-8661

.github/H25-Apr-2025-2414

admin/refresh_spdx/H25-Apr-2025-184138

distro/H25-Apr-2025-7365

doc_build/H25-Apr-2025-194147

docs/H25-Apr-2025-320199

examples/H25-Apr-2025-1,3611,080

licenses/H25-Apr-2025-3,1062,596

rules/H25-Apr-2025-1,7981,575

tests/H25-Apr-2025-631410

tools/H25-Apr-2025-432304

.gitignoreH A D25-Apr-202588 65

BUILDH A D25-Apr-20251.6 KiB6556

CODEOWNERSH A D25-Apr-20259 21

LICENSEH A D25-Apr-202511.1 KiB203169

METADATAH A D25-Apr-2025431 1816

MODULE.bazelH A D25-Apr-2025602 1713

README.mdH A D25-Apr-20251.7 KiB2822

WORKSPACEH A D25-Apr-20251.8 KiB5139

WORKSPACE.bzlmodH A D25-Apr-2025425 1210

deps.bzlH A D25-Apr-20251.1 KiB2824

version.bzlH A D25-Apr-2025657 1715

README.md

1# rules_license
2
3CI: [![Build status](https://badge.buildkite.com/e12f23186aa579f1e20fcb612a22cd799239c3134bc38e1aff.svg)](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