Skip to content

Commit

Permalink
add documention
Browse files Browse the repository at this point in the history
Signed-off-by: himsgupta1122 <hmsgupt@gmail.com>
  • Loading branch information
himsgupta1122 committed Nov 2, 2022
1 parent 4af07e2 commit 14bc9ac
Showing 1 changed file with 8 additions and 3 deletions.
11 changes: 8 additions & 3 deletions SECURITY.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,16 +7,21 @@

- For nested dependency/sub-deps - In order to enforce package above Vx.y.z, we can add version in the resolutions [section](https://classic.yarnpkg.com/lang/en/docs/selective-version-resolutions/) for all the package sub-deps or specific package sub-dep. For more on version updates please see
[Why](https://classic.yarnpkg.com/lang/en/docs/selective-version-resolutions/#toc-why-would-you-want-to-do-this) and [How](https://classic.yarnpkg.com/lang/en/docs/selective-version-resolutions/#toc-how-to-use-it) to upgrade.
```
- To add the CVEs fix to previous versions, add label ex: backport 1.x.

```
Example: foobar@1.x vulnerable package and 1.y is the fix
step 1:
For direct dependency checks:
run: yarn upgrade foobar@1.y
run: yarn upgrade foobar@1.y to update the package.json
and yarn install to update the yarn.lock file
Step 2.
Check for sub deps foobar in other package.
If foobar@1.x exists for subdeps in yarn.lock file
Then edit the package.json file and add **/foobar@1.y in resolution section as shown below to enforce the 1.y.
'resolutions': { "**/foobar": "^1.y",
"**/foo": "^2.x" ,
"**/bar": "^3.k"}

Then run: yarn install for updating yarn.lock file


0 comments on commit 14bc9ac

Please sign in to comment.