One question we've been asked a lot since launching requireSafe: "How is this different from the Node Security Project?"

We've fought that confusion ourselves so today we're announcing that requireSafe will be fully consolidated into the Node Security Project.

This change lets us focus on the one thing we want to do really well: make security a core value of the node community. We couldn't be more excited about simplifying this effort by merging these projects.

Along with this change, we're putting significant work into improving the tooling, education materials, and guidance that the community ...

Continue reading »

requiresafe v2.3.0 was just published and includes a small pile of updates implemented by Nathan LaFreniere based on the feedback by pdehaan and naugtur.

Here is a summary of the updates.

  • added summary formatter similar to the nsp client
  • added vulnerable and patched version display to default formatter
  • cleaned up version numbers for unpatched modules in formatters
  • added --warn-only flag to check command
  • moved linting configuration to a central module, eslint-config-requiresafe
  • removed the scoped dependency for npm < 2.7 support
  • cleaned up the shrinkwrap file

And a bit more detail for some of the more exciting features.

Summary ...

Continue reading »

Combining a continuous integration service like circleci and requireSafe gives you continuous security for your node.js projects.

If you haven't used circleci before, be sure to check out the docs for how to get started before you dive in to integrate requireSafe.

Once you have circleci all setup, it's quite easy to add in requireSafe checking so that you will know right away when a dependency with a known vulnerability ends up in your dependency tree.

First, add requiresafe as a dev dependency by typing

npm i requiresafe --save-dev

Next, add a script to your package.json ...

Continue reading »

If you are using Travis Ci it should take you about 30 seconds to add requireSafe to start continually monitoring your apps for known security vulnerabilities.

If you haven't used Travis before, be sure to check out the docs for how to get started and then dive in to adding requireSafe.

Let's get started.

First add requiresafe as a dev dependency by typing npm i requiresafe --save-dev

Next add a script to your package.json to allow npm to run requiresafe check. Ours looks something like this:

"scripts": { "test": "lab -a code -t 100 -L", "requiresafe": "requiresafe check ...

Continue reading »

It’s been an exciting past couple of weeks. First we launched the new CLI, then we integrated with Code Climate, and now we are going to ship a couple more integrations and a new, much asked for enterprise feature: exceptions.

Grunt & Gulp

We know not everyone uses the same tools for their dev/CI process, so the CLI might not be enough for you. To help make requireSafe accessible to everyone we’ve released grunt-requiresafe and gulp-requiresafe.

Additionally with the release of these integrations we are now at feature parity with the Node Security Project tooling. If you are ...

Continue reading »

We are proud to announce an exciting partnership with Code Climate. Starting today requireSafe will be available as one of the many static analysis tools available on Code Climate’s platform.

requireSafe (available in beta) audits your Node.js modules using a seasoned auditing team and alerts you to vulnerabilities when Node Security Project advisories are created or updated. Of interest specifically is the use of the CLI tool to help identify known vulnerabilities in your own projects.

To make this available to as many developers as possible, we’re releasing requireSafe as an open source “Engine” for the Code ...

Continue reading »

Today we are extremely excited to announce the release of a brand new version of the requireSafe Command Line Interface (CLI).

On the surface it works like the old version, however you will notice a lot of extraneous functionality like logging in or registering has been removed, leaving only the core requiresafe check command in place.

Why did you remove all the goodies?

To be blunt we got a little ahead of ourselves with some features in the beta and decided to burn it down and go back to the basics to make it a better experience for our core ...

Continue reading »

All good things eventually come to an end. All poorly maintained but fun projects tend to as well. After 4 years I’m going to shut down Its last day will be September 30th. was built to serve my needs for extended penetration tests and as a proof of concept for a talk I gave at DEFCON 20 demonstrating the usefulness of such a technique. It met this goal.

I open sourced it a while back, you can find the code here.

Here are some stats from’s run: - 338 people logged in and ...

Continue reading »

We all know that security is hard. But it’s often hard in an advanced-math kind of way: cryptography, encryption, hashing algorithms, cipher suites, elliptic curves, and all the rest are challenging subjects that are not easy to understand.

By contrast, our topic for today - internationalization - is hard in a messy-reality kind of way. Internationalization (often called “i18n” for short because who wants to keep typing those 18 letters between the “i” and the “n”?) involves some exceedingly complicated matters, including:

  • thousands of human languages
  • dozens of scripts (Latin, Cyrillic, Arabic, Kanji, Runic, etc.) used to write those languages
  • 1 ...
Continue reading »

As of right now there really isn't a great source for all things node security news, and we want to change that.

Starting May 20, we're going to start sending out a security newsletter — a Node Security Newsletter that will get dispatched every two weeks.

But we want to collaborate on curating that news with you. We need your suggestions, hacks, most helpful advisories, etc. – all of the things that you feel would be the best gathering of valuable info for us to share across the Node community.

Sign up to get on the Node Security Newsletter mailing ...

Continue reading »