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

@reason.co/vunlscan

v0.0.9

Published

Scan a project for known vulnerabilties and output a PDF report.

Downloads

5

Readme

Vunlscan

v0.0.4

This is an internal Reason tool for vunl scanning.

It will generate a PDF that you can save to artifacts and then pass onto client.

Add to your pipeline

Because Vunlscan is a private npm package you need to set an NPM_TOKEN environment variable and configure npm to use it. Create a file called .npmrc in your project with the following contents:

//registry.npmjs.org/:_authToken=${NPM_TOKEN}

The variable in this file is literal and should not be replaced with the token. Now you can set NPM_TOKEN via Bitbucket's repository variables or manually in your pipeline file with export NPM_TOKEN=...

Then add a script to run with your required config:

# NPM_TOKEN="MAKE SURE THIS IS IN ENV VARS" # add this if you dont have an install step 
lasttag=$(git describe --abbrev=0 --tags) # abbrev'd - or whatever you want your version to be
whitelistpath=$(pwd)/packages/@project/componenet/audit-whitelist.json
scanpathpath=$(pwd)/packages/@project/componenet/retail-insights-app
projectname="App name here"

vunlscan --scanpath="$scanpathpath" --version="$lasttag" --whitelist="$whitelistpath" --projectname="$projectname"

You will need to run your pipeline with an Image that supports x11

image: msquare/bitbucket-nodejs

What is a 'audit-whitelist.json' ?

This is a whitelist file to accept vulnerabilities.

For OSS vulnerabilities, you need to put in the ID (from output) and description (why it is whitelisted), if it needs to be hidden from the report, set "hide" to true.

For HawkEye vulnerabilities, you add a _hawk node and it's ID and description (why it is whitelisted).

If there are items (that are not hidden) in the whitelist, it will add an appendix to the report.

{
  "node": [
    {
      "id": "61538021-1545-4bc3-a154-15b7441d11c3",
      "description": "False negative captured by node environment - Set this to hide:true",
      "hide": true
    },
    ...
  ],
  "_hawk": [
    {
      "id": "files-secrets-.env-58",
      "description": "Env file does not contain any sensitive information"
    },
    {
      "offender": "some-file.js",
      "description": "Or you can exclude a file"
    }
  ]
}