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.
hmz007 36ed224bac
Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a)
1 year ago
..
.bazelci Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
.github Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
admin/refresh_spdx Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
distro Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
doc_build Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
docs Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
examples Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
licenses Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
rules Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
tests Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
tools Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
.gitignore Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
BUILD Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
CODEOWNERS Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
LICENSE Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
METADATA Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
MODULE.bazel Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
README.md Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
WORKSPACE Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
WORKSPACE.bzlmod Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
deps.bzl Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
version.bzl Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago

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.