lice-comb
A Clojure library for software license detection. (by pmonks)
reuse-tool
reuse is a tool for compliance with the REUSE recommendations. (by fsfe)
| lice-comb | reuse-tool | |
|---|---|---|
| - | 10 | |
| 6 | 352 | |
| - | 2.9% | |
| 9.0 | 9.1 | |
| 6 days ago | 2 days ago | |
| Clojure | Python | |
| Apache License 2.0 | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
lice-comb
Posts with mentions or reviews of lice-comb.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning lice-comb yet.
Tracking mentions began in Dec 2020.
reuse-tool
Posts with mentions or reviews of reuse-tool.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-06-29.
-
Releasing AGPL3 project: SPDX vs full notice text and other questions
The SPDX header is due to a project called REUSE, which is spearheaded by the FSF Europe. You can read more about the project here. Basically you just have to add the copyright header in the format
-
License of the input data
I do add my personalized input data into the public repository where I upload my solutions. I add complete reuse-compatible licensing information to my files.
-
How to license my code if a component is gpl?
For projects that include vendored libraries under different licenses, it is becoming common to use Debian's copyright file format to describe which licenses apply to which source files. The data is usually placed in a file called /.reuse/dep5 (see the FSFE's Reuse Software project). If you want to enable fine-grained license checks, you can also include a machine-readable SPDX-License-Identifier line in each file.
- REUSE SOFTWARE – make licensing easy for humans and machines alike
-
Should I put license notices in all my source code files?
Check out https://reuse.software
- LwESP library for ESP32 and ESP8266
- Reuse Software Licensing
- Reuse: Make licensing easy for humans and machines alike
-
README/HACKING.md does not specify license and copyright terms
Putting the copyright and licensing information in every file was very common, and FSFEs reuse has some interesting specifications if compliance is an issue (e.g. I do not fully understand what the OpenSSL license included in the app-ios/tutanota/include folder covers, which also includes a APL-licensed files) - but thats a different topic.
-
Should I go with GPLv3?
No, but it's a good idea to mention the license you're using. You can use REUSE (https://github.com/fsfe/reuse-tool).
What are some alternatives?
When comparing lice-comb and reuse-tool you can also consider the following projects:
spdx-license-matcher - A tool to match license text with SPDX license list using a an algorithm with finds close matches. It follows SPDX Matching guidelines to keep the substantial text as well as ignore the replaceable text for matching purposes.
degiro-trading-tracker - Simplified tracking of your investments