bazelbuild / rules_license

bazelbuild/rules_license Issues

gather_licenses_info does not seem to capture license of external packages
Updated 3 months ago2
Provide a user extensible compliance linter
Updated 4 months ago2
How to use rules_license on the envoy project ?
Updated 4 months ago
rules_license lacks compatibility with the renamed package_metadat field
Closed 6 months ago1
rules_license lacks compatibility with the renamed package_metadat field
Updated 6 months ago
SPDX formatted BOM
Updated 7 months ago3
package_info should have a field for the vendor sbom
Updated 8 months ago1
Add `additional_info` attribute to `license` rule.
Updated 8 months ago3
Create py_binary target for add_licenses.py
Updated 8 months ago
Update add_licenses.py to query for SPDX licenses on its own
Updated 8 months ago
style: release whole repository
Updated 8 months ago2
Update rules_jvm_external so package_info is written to generated BUILD files
Updated 8 months ago
Update release automation so that 'push a tag' is the only action needed
Updated 8 months ago
Add CI test to check SPDX licenses are up-to-date
Updated 8 months ago
`license_text` should not be mandatory
Updated 8 months ago1
licenses_info_to_json failed as the TransitiveLicensesInfo is empty
Updated 8 months ago
Tools should not be in the default metadata gathering
Updated 9 months ago1
Monthly public engineering meeting
Updated 9 months ago
gather_licenses_info_common does not traverse inputs via label_keyed_dict(s)
Updated 9 months ago
gather_licenses does not traverse exports_files
Closed 9 months ago1
Populate third party license meta data
Updated 9 months ago2
Manifest example test doesn't work
Updated 9 months ago2
Add actual license text to JSON output
Updated 9 months ago1
Avoid duplicate packages
Updated 9 months ago
Mechanism to exclude generating rules as target dependencies
Updated 9 months ago1
The checker_demo.py will always write an empty license_texts file
Updated 9 months ago1
Rules should be able to customize how licenses propagate through them.
Updated 9 months ago
The rules to declare licenses and their kinds should be in a distinct bazel package from the ones that consume them.
Updated a year ago1
release 0.0.6 rules/compliance.bzl is broken
Closed a year ago1
Missing license file should not be a failure
Closed a year ago2
Following example in examples/manifest does not work
Closed a year ago2
Add stardoc generation
Closed a year ago1
Avail human readable license name(long_name) for gather_licenses_info_and_write
Closed a year ago
TransitiveLicensesInfo was made private, breaking downstream customers
Closed a year ago2
license.license_text should support labels
Closed a year ago3
set up presubmit testing
Closed 2 years ago3
Find a new meeting time for the regular engineering meeting
Updated 2 years ago1
Rewrite tests to be less brittle than golden file matching
Updated 2 years ago
Expand list of attributes inspected when collecting license information
Updated 2 years ago3
refactor repository
Closed 2 years ago1
Allow rulesets to adopt rules_license
Closed 2 years ago3
Add generic license_kinds rules for legacy Bazel licenses types.
Closed 2 years ago2
License requirements
Updated 2 years ago
Add a How-To document
Updated 2 years ago
Create a list of common conditions.
Updated 2 years ago1
Turn on github pages to hold end user documentation
Updated 2 years ago
update SPDX license list
Closed 2 years ago
spdx license list update should keep licenses sorted.
Updated 2 years ago
Apply to Bazel: tracking bug
Updated 2 years ago
Add license_kind rules for SPDX list
Closed 4 years ago