Skip to content

Commit b193380

Browse files
authored
Merge pull request #34 from shadowspawn/feature/20-off-by-one
Section 5.6 has wrong text for Do and Otherwise
2 parents 01bbc91 + 3bd3883 commit b193380

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

readme.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1895,11 +1895,9 @@ license-checker --summary --failOn BSD
18951895
<br/><br/>
18961896

18971897
## ⚪ ️5.6 Constantly inspect for vulnerable dependencies
1898-
:white_check_mark: **Do:** Licensing and plagiarism issues are probably not your main concern right now, but why not tick this box as well in 10 minutes? A bunch of npm packages like license check and plagiarism check (commercial with free plan) can be easily baked into your CI pipeline and inspect for sorrows like dependencies with restrictive licenses or code that was copy-pasted from Stackoverflow and apparently violates some copyrights
1899-
<br/>
1900-
1898+
:white_check_mark: **Do:** Even the most reputable dependencies such as Express have known vulnerabilities. This can get easily tamed using community tools such as [npm audit](https://docs.npmjs.com/getting-started/running-a-security-audit), or commercial tools like [snyk](https://snyk.io/) (offer also a free community version). Both can be invoked from your CI on every build
19011899

1902-
**Otherwise:** Even the most reputable dependencies such as Express have known vulnerabilities. This can get easily tamed using community tools such as [npm audit](https://docs.npmjs.com/getting-started/running-a-security-audit), or commercial tools like [snyk](https://snyk.io/) (offer also a free community version). Both can be invoked from your CI on every build
1900+
**Otherwise:** Keeping your code clean from vulnerabilities without dedicated tools will require to constantly follow online publications about new threats. Quite tedious
19031901

19041902

19051903
<br/>

0 commit comments

Comments
 (0)