You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
1 year ago | |
|---|---|---|
| .. | ||
| .bazelci | 1 year ago | |
| .github | 1 year ago | |
| admin/refresh_spdx | 1 year ago | |
| distro | 1 year ago | |
| doc_build | 1 year ago | |
| docs | 1 year ago | |
| examples | 1 year ago | |
| licenses | 1 year ago | |
| rules | 1 year ago | |
| tests | 1 year ago | |
| tools | 1 year ago | |
| .gitignore | 1 year ago | |
| BUILD | 1 year ago | |
| CODEOWNERS | 1 year ago | |
| LICENSE | 1 year ago | |
| METADATA | 1 year ago | |
| MODULE.bazel | 1 year ago | |
| README.md | 1 year ago | |
| WORKSPACE | 1 year ago | |
| WORKSPACE.bzlmod | 1 year ago | |
| deps.bzl | 1 year ago | |
| version.bzl | 1 year ago | |
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:
- Mailing list: bazel-ssc@bazel.build
- Monthly eng meeting: calendar link
- Latest docs
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.