Check NPM package licenses (by davglass)

License-checker Alternatives

Similar projects and alternatives to license-checker

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.
  • Big Changes Ahead for Deno
    13 projects | | 15 Aug 2022
    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.



  • Italian Courts Find Open Source Software Terms Enforceable
    2 projects | | 27 Dec 2021
    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.



  • Node.js Packages and Resources
    106 projects | | 6 Sep 2021
    license-checker - Check licenses of your app's dependencies.
  • Home Screen Shortcuts in React Native (with Expo)
    4 projects | | 19 Aug 2021
    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?
    2 projects | /r/opensource | 28 May 2021
    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 or an equivalent license checking service in your project language to ensure that everything is kosher
  • A note from our sponsor - Sonar | 30 Sep 2023
    Sonar helps you commit clean code every time. With over 300 unique rules to find JavaScript bugs, code smells & vulnerabilities, Sonar finds the issues while you focus on the work. Learn more →


Basic license-checker repo stats
5 months ago
Collect and Analyze Billions of Data Points in Real Time
Manage all types of time series data in a single, purpose-built database. Run at any scale in any environment in the cloud, on-premises, or at the edge.