Another week, another batch of changes

This week, the nsp team was focused primarily on improving our backend processes and some automation tools to help us track down those pesky vulnerabilities for you.

Along with some minor bug fixes, we have a couple of fun new features for our users too.

Badge generator

No longer do you have to create the markdown to add your nsp badge to your projects. We now show your badge at the top right of your project’s page. Click that badge and you’ll get a handy little dialog that contains both the direct link to the badge, and a markdown snippet that you can copy and paste right into your README.md.

View check results for any public module

Ever been curious about the security status of your favorite module in npm?

Try going to https://nodesecurity.io/check/express to see some details right in your browser. Just change the module name in the url for whatever module you want to check out. We’ve included a nice little drop down so you can pick whatever version of the module you’d like to see the results for too.

Rate limiting

While this hasn’t been implemented just yet, in the very near future we’ll be turning on rate limiting for several routes in the API. Users that run lots of checks or use it for commercial purposes will want to keep an eye out for errors, and contact us to talk about becoming a partner and lifting those limits. Note that nsp Live will not have these limitations and is a better way to continuously run checks against your projects.

How you can help

Have an idea for a new feature? Found a bug? Please let us know and we’ll do what we can to take care of things. Also if you found nsp Live useful, please share that with the world and help others find it useful too.