Setting up projects and running tests can vary based on what language is used and whether or not the test runs from the app UI, the CLI, or specific API endpoints.
This page is meant to direct users to the proper documentation for specific import errors and information on what to expect when using the CLI versus the UI in the app.
Project import error documentation
- Project Import docs (covers several languages)
- Private repo tests count toward monthly usage limits (to avoid this, ensure the repo is publicly accessible)
- Set a Snyk CLI project to open source (ensure tests do not run as private)
- Snyk actions (Github actions for Snyk, language-dependent)
- Snyk API (see explanation of API vs CLI vs Snyk integration in introduction)
CLI vs. App UI
Generally, using the CLI will give more coverage and have the most up-to-date functionality. This is simply because the CLI has the ability to make more granular tasks where the App UI (sny.io) must be usable for specific tasks based on specific feedback and reports. Simpler tasks are done more easily through the UI but aren't as flexible and are meant for basic coverage and to speed up low effort task completion.
See our article on Why did Snyk CLI discover different dependencies document for more information.
Monthly scan counts
To see the current number of tests for your account:
Navigate to app.snyk.io/org/theorgname/manage/usage
- RED: Test category--separated by product and private
- BLUE: Current count against the account maximum
- GREEN: Unlimited tests are shown without a bar or count
For more information about the usage page, check out our usage page details article.
Contact the account's Customer Success representative. The representative will open tickets, contact support, and upgrade the issue as needed.
Bringing awareness to missing documentation will ensure that our documentation team will address and rectify the problem. We appreciate feedback and strive to make using Snyk ridiculously easy.