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

pack-it-in

v0.0.10

Published

Analyses Licences of included NPM packages to ensure that they conform to your specifications.

Downloads

45

Readme

pack-it-in

A License Manager for Node.js

Overview

Pack-it-in is meant to simplify the process of including FOSS in your project by analysing the licenses of the software you are including within your project and generating an easy to read Excel report detailing the licenses used by each component of your project. There is also no need to worry about analysing your indirect dependencies. The dependencies of your dependencies will automatically be analysed and included within the report.

Written with complex, commercial grade software in mind, pack-it-in was written to be easily configurable in terms of types of licenses permitted for one’s project as well as the format of the report generated. In addition to this type of configuration, there is also rudimentary support for other forms of package analysis. The currently released version includes basic support for handling cryptographic packages, this will be further detailed below where the configuration file is detailed.

Using pack-it-in

To install pack-it-in, Simply run

npm install -g pack-it-in

To run the programme, using the default configuration, you can simply run:

node pack-it-in

This will analyse the project within the current directory, should one exist, and output and the excel report to license-details.xlsx which will be located in the same directory where you ran pack-it-in.

To see an example of the report generated by pack-it-in (coincidentally, the report made for pack-it-in) you can see an example in license-details.xlsx.

As one can observe, there are two spreadsheets generated. The first sheet called "3rd Party" lists all of the runtime dependencies of the project, while the second details any modules which are dependencies only within a development environment (as well as any runtime dependencies of those development dependencies).

If you would like to run the programme using a custom configuration file, one can simply run

node pack-it-in -c path/to/config/file.json

One can also use the longer option and run

node pack-it-in - - config=path/to/config/file.json

NPM Legacy Mode

As of version 0.10 pack-it-in supports npmv8 package-lock files. If you are using an older version of NPM you will have to use the --l or --legacy flag.

Configuration

A commented version of the default configuration file can be found in default-config.jsonc. This file provides a detailed explanation of what each option does and how one can customise the functionality of pack-it-in to their own needs. As the project grows, default-config.jsonc will grow so that it remains fully accurate.

A link to this default config file can be found "HERE"

Contributing

If you would like to contribute to pack-it-in, please reach out to us at [email protected] and we will let you know how you can get involved with the project.