-
Is it possible to add an [SPDX](https://spdx.org/licenses/) `license ID` from the `Identifier` column in each of the found libraries licenses. It opens new possibilities for the output of this great t…
-
Basically this: https://github.com/mdogan/homebrew-zulu/blob/master/.github/workflows/upgrade.yml
-
Having a typo in the license info would be a bummer. What would be the best way to validate licenses?
Would https://github.com/spdx/tools be a good idea?
-
# Goal
Track licenses of used tools in dotfiles.
# Proposal
Incorporate a LICENSE file into each subfolder. For 1:1 mapping of folder to tools, the tool will simply state the license of the too…
-
-
- [ ] Keep work on the common evaluation of indicators: https://docs.google.com/spreadsheets/d/1H5-15yCrM065k-u0seanQZ47BQ-WUUFVwGJFUNHwcBE/edit?gid=1759105918#gid=1759105918
- [ ] Support for creati…
orviz updated
1 month ago
-
If a package is released under the terms of two licenses the manual says
> Multiple licenses should be separated by commas, Example: `GPL-3.0-or-later, custom:Hugware`.
However, this does not ma…
-
There are discrepancies between FSF's canonical `GPL-1.0` and `GPL-2.0` texts and their associated SPDX templates that cause matching to fail in downstream software that performs matching.
Specific…
-
Issue #1736 includes the interesting point that AppStream (widely used in Linux distributions) is yet another program which uses SPDX License Identifiers to attempt to determine whether software is fr…
-
See https://reuse.software/
There are several levels:
- [x] SPDX-License-Identifier (this has long been there)
- [x] SPDX-FileCopyrightText (See https://github.com/nexB/scancode-toolkit/issues/18…