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

security-audit-nodejs

v0.1.2

Published

A collection of security tests for your Node.js project

Downloads

8

Readme

security-audit-nodejs

A collection of security tests for your Node.js project.

Installation

npm install security-audit-nodejs --save-dev

Usage

This module provides no API. It provides a script for you to include in your package.json file, called simply security-audit-nodejs. You can add it to your "test" script for example:

{
  "scripts": {
    "test": "eslint . && security-audit-nodejs"
  }
}

Every time you run npm test now, it will run a wide array of security tests on your project. The tests may take a while, so it can be beneficial to put it in a separate script and run it as part of your CI setup:

{
  "scripts": {
    "test:security": "security-audit-nodejs"
  }
}
npm run test:security

If any vulnerabilities are found, the program will exit with a non-zero exit code.

Arguments

You can pass the following to security-audit-nodejs:

  • --severity [low|medium|high|critical] Only vulnerabilities of this level or higher will be shown.

Ignoring vulnerabilities

It can happen that a module you use has a vulnerability, but the way you use it guarantees you that that vulnerability will not expose itself. When you're really sure about this, you can add the vulnerability ID to .security-audit-nodejs-ignore in your project-folder. Every vulnerability is assigned a unique ID, that is shown in the output of the test you run. Every ID you mention in the ignore file must be on a new line. You may add comments to the line as follows: some:vulnerability-id # this is a comment. This way you can document why you explicitly chose to ignore a particular vulnerability.

License

MIT