npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

infer-license

v1.1.1

Published

Infer license from text

Downloads

2

Readme

Infer License

NPM

Code Climate Build Status dependencies Status

Sometimes, you need to know what license a module is provided under.

While many modules report their license via the package.json file (for NPM modules), some do not.

Instead, the license is embedded in the README or in a LICENSE file.

This is fine for humans, but not so great for computers.

This module can infer the appropriate license when fed the contents of a relevant file and return the appropriate SPDX identifier.

In addition, it can scan a file for links to licenses at spdx.org and opensource.org. At the moment, these are not checked to confirm that they are valid SPDX ids or that the links actually lead to a license.

Example

const infer = require('infer-license');

fs.readFile('LICENSE.md', function (err, contents) {
    console.log(infer.inferLicense(contents)); // 'MIT'
});
const infer = require('infer-license');

fs.findLicenseLinks('LICENSE.md', function (err, contents) {
    console.log(infer.inferLicense(contents)); // 'BSD-3-Clause'
});

Dependencies

None!

Testing

Currently, this tool uses SPDX license files and, for each one, confirms that

  • The license is correctly identified, i.e. it is identifed with the correct identifier
  • The license is definitively identified, i.e. it is not identified with an incorrect identifier

Support

Currently, this tool can identify the following licenses

  • MIT
  • BSD
  • ISC
  • LGPL
  • Apache
  • Ecplise (EPL)
  • WTF

API

The inferLicense function will return the inferred SPDF identifier (where it can).

The findLicenseLinks function will return the inferred SPDF identifier (where it can). If links to multiple licenses are found, it will be in the form of (X OR Y OR Z).

There are a set of is<Type> functions that will return a truthy value if the provided text conforms with the license of type <Type>.