nodejs/nodebestpractices
1
0
Fork 0
mirror of https://github.com/goldbergyoni/nodebestpractices.git synced 2025-11-01 01:56:06 +08:00
Code Issues Packages Projects Releases Wiki Activity

Fixed some typos

Browse Source
This commit is contained in:
Bruno Scheufler
2017-11-14 14:13:15 +01:00
committed by Refael Ackermann
parent c399b3de49
commit 8d530d84e1
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
sections/production/detectvulnerabilities.md
View File

@ -4,8 +4,8 @@
### One Paragraph Explainer ### One Paragraph Explainer
Modern node applications has tens and some time hundred dependencies. If any of the dependencies Modern Node applications have tens and sometimes hundreds of dependencies. If any of the dependencies
you use has a known security vulenrability your app is vlnurable as well. you use has a known security vulnerability your app is vulnerable as well.
The following tools automatically check for known security vulnerabilities in your dependencies: The following tools automatically check for known security vulnerabilities in your dependencies:
[nsp](https://www.npmjs.com/package/nsp) - Node Security Project [nsp](https://www.npmjs.com/package/nsp) - Node Security Project
[snyk](https://snyk.io/) - Continuously find & fix vulnerabilities in your dependencies [snyk](https://snyk.io/) - Continuously find & fix vulnerabilities in your dependencies
@ -13,6 +13,6 @@ The following tools automatically check for known security vulnerabilities in yo
<br/><br/> <br/><br/>
### What Other Bloggers Say ### What Other Bloggers Say
From the [StrongLoop](https://strongloop.com/strongblog/best-practices-for-express-in-production-part-one-security/): From the [StrongLoop](https://strongloop.com/strongblog/best-practices-for-express-in-production-part-one-security/) blog:
> ...Using to manage your application’s dependencies is powerful and convenient. But the packages that you use may contain critical security vulnerabilities that could also affect your application. The security of your app is only as strong as the “weakest link” in your dependencies. Fortunately, there are two helpful tools you can use to ensure of the third-party packages you use: and requireSafe. These two tools do largely the same thing, so using both might be overkill, but “better safe than sorry” are words to live by when it comes to security... > ...Using to manage your application’s dependencies is powerful and convenient. But the packages that you use may contain critical security vulnerabilities that could also affect your application. The security of your app is only as strong as the “weakest link” in your dependencies. Fortunately, there are two helpful tools you can use to ensure of the third-party packages you use: and requireSafe. These two tools do largely the same thing, so using both might be overkill, but “better safe than sorry” are words to live by when it comes to security...