Installation and Authentication
PreviousMigrating from Safety CLI 2.x to Safety CLI 3.xNextScanning for Vulnerable and Malicious Packages
Last updated
Was this helpful?
Last updated
Was this helpful?
To scan and secure Python projects, you first need Safety CLI version 3 to be installed on your machine.
If the safety command is not found, or your safety version is less than 3.0, you need to install Safety version 3 using the following command before continuing:
When installation of Safety version 3 has been confirmed, launch your terminal and authenticate using one of the methods outlined below.
Customers on our Free and Team plans will log in using an email and password defined when you .
In your terminal, type:
Your default browser will open and you will be asked to authenticate using your Safety username and password. Login via Google is currently supported, and support for additional SSO providers will be added soon.
Once logged in, return to your terminal to verify Safety is authenticated with your account details by typing:
Enterprise customers can leverage the method described above or SAML-based authentication, allowing users to be authenticated using organization-specific identities. The latter preserves approved authentication flows and prevents access to anyone not registered in your internal identity platform.
As above, when installation has been confirmed, in your terminal, type:
This will open your browser to authenticate the Safety CLI tool using your work email address and password. If your organization uses SAML authentication, you will be redirected to your corporate login page.
Once logged in, return to your terminal to verify Safety is authenticated with your account details by typing:
If you are unclear as to which method your organization uses, please contact your administrator or email us at .
