Usage settings
Last updated
Last updated
More information
Snyk privacy policy© 2024 Snyk Limited | All product and company names and logos are trademarks of their respective owners.
In your Group or Organization, select Settings > Usage to view Snyk usage details for your Group or Organization:
Test usage: the number of tests used
Contributing developers: the number of developers contributing to Projects
For more information about test frequency settings, see Project actions on the Project Listings page, where bulk actions are also explained.
The Test Usage section shows how many tests you are using over the current billing period:
Test limits vary for Snyk products and plans.
For the Free plan, the limis are: Open Source, 400 tests; Code, 100 tests; IaC, 300 tests; Container, 100 tests.
See the Plans and pricing page for more details.
See What counts as a test? for details of how Snyk counts tests.
Snyk has developer counts are for the GitHub, GitHub Enterprise, and GitLab integrations and for the Snyk CLI.
Snyk defines contributing developers as developers having made a commit to a private repo monitored by Snyk in the last 90 days.
The Contributing developers for Git and CLI integrations section shows contributing developer counts, both at the Organization level and the Group level.
The counts indicate the number of contributing developers to the default branch of the private repos connected with the integration.
Snyk does not count contributions to public (open-source) repos because the pricing model is based on the number of contributing developers to private repositories.
An example of the count of contributing developers follows:
Total unique contributors across all integrations: the number of contributors across all the integrations in your Snyk account. Contributing developers are only counted once, even if they have contributed to multiple integrations or multiple repositories.
Breakdown by integration: the number of contributors, Organizations, and repos in that integration.
Each contributor is counted by the author email field, which is set within the local Git configuration in the developer’s machine.
