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

depalyzer

v0.0.7

Published

A tool which determines whether an npm module modifies the built-in javascript types like `Array`, `Object`, etc.

Downloads

3

Readme

depalyzer

A tool which determines whether an npm module modifies the built-in javascript types like Array, Object, etc.

Installation

You can either install depalyzer globally:

sudo npm install -g depalyzer

This allows you to use it like traditional binary:

depalyzer true-html-escape

Or install it locally:

npm install depalyzer

And run it as follows:

./node_modules/.bin/depalyzer true-html-escape

Usage

depalyzer [--verbose] module-name
  • module-name: the name of the npm module to be analyzed
  • --verbose: optionally enable detailed output

Output

For a module with > 1 modification to build-in types, the script will exit with the code 1 and you'll see output like:

padowan@pure-deps> depalyzer true-html-escape
true-html-escape includes 3 dependencies...
✓ 3 globals were not modified.
   ✓ Object.prototype
   ✓ Boolean.prototype
   ✓ Math
✗ FAILURE: 10 globals were modified, with 623 total modifications.
   ✗ Array
   ✗ Array.prototype
   ✗ Object
   ✗ Number
   ✗ Number.prototype
   ✗ Function
   ✗ Function.prototype
   ✗ Boolean
   ✗ Date
   ✗ Date.prototype

For a module without modifications, the script will exit with code 0 and you'll see output like:

padowan@pure-deps> depalyzer escape-html
escape-html includes 0 dependencies...
✓ Success: No globals were modified.
   ✓ Array
   ✓ Array.prototype
   ✓ Object
   ✓ Object.prototype
   ✓ Number
   ✓ Number.prototype
   ✓ Function
   ✓ Function.prototype
   ✓ Boolean
   ✓ Boolean.prototype
   ✓ Date
   ✓ Date.prototype
   ✓ Math

Why?

It's hard to know what you'll get when you install a new npm module. This tool allows you to quickly check for modules which modify the built-in types, like the 623 additions and modifications made by the true-html-escape library to types like Array and Date.

These can and do have real side-effects on your software. This tool helps developers avoid those side-effects.

May the force be with you in your journey for pure dependencies young padowan.

What's next:

  • [ ] Tests!

  • [ ] Expand the types which are monitored for mutations

  • [ ] Options for disabling color, fancy checks n' such

  • [ ] Expose API for programmatic use, something like:

    const depalyzer = require('depalyzer');
    const results = depalyzer('true-html-escape');
    if (results.hasGlobalModifications()) {
      console.error('Oh noes!')
    }