What is Snyk checking when it checks a package?
A package is code someone else wrote that your app uses. Snyk Open Source checks those dependencies for reported issues. It is a separate check from Snyk Code, which analyzes your own source. Confirm which you’ve connected so one passing result doesn’t stand in for both.
Why can one project consume several tests?
On plans with test limits, the product and the way you run a check can affect how many tests it uses. Credit-based plans use a separate rate card. For Code and Open Source, it measures credits per active contributor per day. List the repositories, checks and contributors you expect before comparing plans.
What happens after a package is flagged?
Give someone responsibility for reviewing the suggested change. Update the package in a disposable copy and have the team check that sign-in, saving and checkout still work if the app uses them. Keep track of issues you postpone and when you’ll look again.
How would you decide whether an update is ready?
Imagine a fictional booking app gets a package alert. Write down what would convince you an update is safe to release.
- List what can breakInclude submitting a booking, seeing its confirmation and finding it later.
- Assign the decisionWrite who checks the result and who can approve a temporary delay.