3.0.0

Safety 3.0.0 major version release!

• Safety 3.0.0 is a significant update to Safety CLI from 2.x versions, including enhancements to core features, new capabilities, and breaking changes from 2.x.
• See our Blog article announcing Safety CLI 3 for more details on Safety 3 and these changes
• See Migrating from Safety 2.x to Safety CLI 3 for notes and steps to migrating from Safety 2 to Safety 3

2.3.5

Version 2.3.5

2.3.4

Version 2.3.4

2.3.3

Version 2.3.3

2.3.2

• Fixed #423: Bare output includes extra line in non-screen output with no vulnerabilities.
• Fixed #422: ResourceWarning (unclosed socket) in safety v.2.3.1.
• Fixed telemetry data missing when the CLI mode is used.
• Fixed wrong database fetching when the KEY and the database arguments are used at the same time.
• Added SAFETY_PURE_YAML env var, used for cases that require pure Python in the YAML parser.

2.3.1

Safety 2.3.1 release

2.3.0

What's Changed

• Safety Alerts: GitHub PRs and GitHub issues support by @cb22 in #411
• Safety 2.3.0 patch by @cb22 in #415

Full Changelog: 2.2.1...2.3.0

2.2.1

What's Changed

• Pull from Master by @yeisonvargasf in #410
• Common fixes for next release by @yeisonvargasf in #412
• 2.2.1 Patch by @yeisonvargasf in #414

Full Changelog: 2.2.0...2.2.1

2.2.0

What's Changed

• Eat stderr messages from git commands. by @tarmack in #399
• Update from master branch by @yeisonvargasf in #404
• Remove AppVeyor and Travis by @yeisonvargasf in #405
• Using dparse to read requirements and fixes for custom integrations by @yeisonvargasf in #406
• Safety 2.2.0 patch by @yeisonvargasf in #407

New Contributors

• @tarmack made their first contribution in #399

Full Changelog: 2.1.1...2.2.0

Safety 2.0.0 and Safety GitHub Action - Python Dependency Scanner

PyUp is excited to release Safety 2.0 CLI and Safety as a GitHub Action!

Compared to previous versions, Safety 2.0 will be a significant update that includes new features and refactors, resulting in breaking changes to some inputs and outputs. The new GitHub Action enables you to configure Python dependency security and compliance scans on your repositories on new commits, new branches, pull requests, and more.

Summary:

• Safety 2.0 major release (notes below) and GitHub Action release

Updated outputs:

• Text & screen output: Upgraded the text and screen outputs, removing the old table style and adding new data and formats to vulnerabilities.
• JSON output: New and updated JSON output (breaking change). Safety adds all the possible information in the JSON report. The structure of this JSON file has been improved.
• Improved the support for exit codes. There are now custom exit codes with detailed information about the result. Examples include: VULNERABILITIES_FOUND and INVALID_API_KEY.
• Added remediations (fix recommendations) sections to outputs. Now, Safety will suggest the steps to fix a detected vulnerability when an API key is used.
• Added new summary meta-data data to the reports showing the Safety version used, the dependencies found, the timestamp, the target scanned, and more. These data are included in the text, screen, and JSON output for improved audit capabilities.
• Added more info per vulnerability, including URLs to read more about a vulnerability and/or a package.

New command line flags:

• New command line flags
  • The --output flag replaces --bare, --text, --screen, and --json flags. In this new release, examples would be: --output json or --output bare.
  • The --continue-on-error flag suppresses non-zero exit codes to force pass CI/CD checks, if required.
  • The --debug flag allows for a more detailed output.
  • The --disable-telemetry flag has been added to disable telemetry data
  • The --policy-file flag to include a local security policy file. This file (called .safety-policy.yml, found in either the root directory where Safety is being run or in a custom location) is based on YAML 1.2 and allows for:
    • Ignoring individual vulnerabilities with optionally a note and an expiry date.
    • Filtering vulnerabilities by their CVSS severity. (CVSS data is only available for some paid accounts.)

Other

• Dropped support for Python < 3.6
• The free version of the Safety vulnerability database is downloaded from a public S3 bucket (via PyUp.io) and no longer from GitHub. This free database is only updated once a month and is not licensed for commercial use.
• Telemetry data will be sent with every Safety call. These data are anonymous and not sensitive. This includes the Python version, the Safety command used (check/license/review), and the Safety options used (without their values). Users can disable this functionality by adding the --disable-telemetry flag.
• Added validations to avoid the use of exclusive options.
• Added announcements feature to receive informative or critical messages from the PyUp Safety team.
• Increased test coverage.
• Now Safety can be used as a dependency in your code
• Added Safety as a Github Action
• Improved the help text in the CLI
• Added the --save-json flag