Comments (1)
Has there been any thought given to a design here? Should it be part of package_info, or a new rule? I was thinking of a new package_sbom rule for example, and it could take sbom filename(s), and perhaps an optional format specifier (for example, the various syft output formats perhaps?). These could then be used like package_info, in that they are applied to a set of targets via either package rule's default_applicable_licenses, or through an explicit entry in a target's applicable_license attribute. This could then be gathered when traversing the targets and then somehow (tbd) integrated into the final output. If that final output is spdx, then perhaps an spdx input would be an externalRefs. Or perhaps it could be integrated directly into the final output as an option.
from rules_license.
Related Issues (20)
- release 0.0.6 rules/compliance.bzl is broken HOT 1
- gather_licenses does not traverse exports_files HOT 1
- Populate third party license meta data HOT 2
- Add actual license text to JSON output HOT 1
- Avoid duplicate packages
- Manifest example test doesn't work HOT 2
- style: release whole repository HOT 2
- Update release automation so that 'push a tag' is the only action needed
- Update rules_jvm_external so package_info is written to generated BUILD files
- How to use rules_license on the envoy project ?
- rules_license lacks compatibility with the renamed package_metadat field
- rules_license lacks compatibility with the renamed package_metadat field HOT 1
- gather_licenses_info does not seem to capture license of external packages HOT 2
- Avail human readable license name(long_name) for gather_licenses_info_and_write
- Mechanism to exclude generating rules as target dependencies HOT 1
- The rules to declare licenses and their kinds should be in a distinct bazel package from the ones that consume them. HOT 1
- TransitiveLicensesInfo was made private, breaking downstream customers HOT 2
- Tools should not be in the default metadata gathering HOT 1
- Provide a user extensible compliance linter HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rules_license.