The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
License-checker Alternatives
Similar projects and alternatives to license-checker
-
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
-
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
deno-lambda
A deno runtime for AWS Lambda. Deploy deno via docker, SAM, serverless, or bundle it yourself.
-
-
-
-
ignite
Infinite Red's battle-tested React Native project boilerplate, along with a CLI, component/model generators, and more!
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better license-checker alternative or higher similarity.
license-checker reviews and mentions
Posts with mentions or reviews of license-checker.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-08-15.
-
Consultant Asking About NPM Software Licenses
I thought that was a fairly weird question. A couple of our APIs run on Ubuntu, which contains GNU software. He has access to our source code, and I had also previously sent him the output of license checker so he really should have been able to answer this himself.
-
A developer-friendly introduction to open source licenses
NPM License Checker
-
Big Changes Ahead for Deno
I don't care whether it's all in one file or in a dozen files, but I want all of that information to be available programmatically in a text file (unlike in a readme or on Github) in a standardized location in a project.
In that respect, package.json is a strict win. Your lack of willingness to use `git blame` to see why you added a line, or lack of reasonable git comments, is not to be blamed on the file.
Complexity is unavoidable. How could you write a tool like license-checker [1] for a Go-based project without having license information in a standardized location? Without the scripts section, how can you create a tool like husky [2] that automatically installs git hooks for a project? Every single part of package.json is there for a good reason; at best you could argue that putting some of it in other files would be aesthetically superior, but that's just bikeshedding.
Complexity isn't de facto bad. Some complexity is required if you want a certain level of functionality to become available. Deno (and Go) are slowly accumulating that "cruft" as people realize that those functions are actually useful or even critical to a mature ecosystem.
[1] https://www.npmjs.com/package/license-checker
[2] https://www.npmjs.com/package/husky
-
Richard Stallman calls for software package systems that help maintain your freedoms
Yes, all npm packages are supposed to have a valid SPDX license identifier, and there is an easy way to recursively check these values
-
Introducing sbomx.com - Software Bill of Materials X
For JavaScript I always used davglass/license-checker as a starting point but it's not being maintained anymore. Then I did similar things for the backend code, put everything together and sent it to the legal and security teams. At some point I thought "There must be a better way!". So, I started building sbomx about one and a half years ago. It's working fine enough to show it to the world and gather some feedback.
-
automatically pull licenses from package.json and put them into a spreadsheet??
Check this package https://www.npmjs.com/package/license-checker
-
Italian Courts Find Open Source Software Terms Enforceable
Good doctors and drivers make mistakes, too, and they still face liability for those mistakes.
I think that if your company is large enough, you should have employees, or pay someone, to mirror your dependencies and automate license checks. There are projects that do the latter already[1][2]. You can loop your lawyers in if licenses change to ensure you don't violate them. If (A)GPL code still ships in proprietary products, that's a process problem that the company needs to solve.
[1] https://github.com/dhatim/python-license-check
[2] https://github.com/davglass/license-checker
-
Node.js Packages and Resources
license-checker - Check licenses of your app's dependencies.
-
Home Screen Shortcuts in React Native (with Expo)
If you don't know what licenses you're currently using, I suggest the license-checker NPM tool.
-
How do I explain the concept of open source software to my boss?
Also, your IT dept is not entirely without concern here, you should be ensuring that you're not violating any open source licenses in your project, and be using something like https://www.npmjs.com/package/license-checker or an equivalent license checking service in your project language to ensure that everything is kosher
-
A note from our sponsor - WorkOS
workos.com | 26 Apr 2024
Stats
Basic license-checker repo stats
10
1,572
0.0
3 months ago
davglass/license-checker is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of license-checker is JavaScript.
Popular Comparisons
Sponsored
Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com