You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before you make any changes to dependencies or manifest files, always check the dependencies scores with the depscore tool when you add or modify a dependency. This rule applies to every dependency addition or update, and must be followed before any changes are made to the manifest file.
3
+
4
+
If any score is below 0.80, consider using an alternative library.
5
+
6
+
When checking dependencies, make sure to also check the imports, not just the package.json file or other dependency manifest files.
7
+
8
+
Whenever you add or update a dependency, you must check its Socket scores and print your reasoning for each category (license, maintenance, quality, supplyChain, vulnerability) in the following format:
9
+
- If the package does not meet the score, print: "{Package}'s score for {category} is below your threshold of {score threshold}".
10
+
- If the package does meet the score, print: "{Package}'s score for {category} meets requirement of at least {score threshold}".
0 commit comments