Safety v3.5.1 is now available. Upgrade using "pip install -U safety"
Safety Firewall
LogoLogo
Safety PlatformResearchSign Up
  • Introduction to Safety
  • Safety Firewall
    • Introduction to Safety Firewall
    • Installation and Configuration
      • Uninstalling Firewall
    • Using Firewall
      • Working with Codebases
      • Firewall Monitoring and Management
      • Firewall Policy Management
      • Troubleshooting
  • SAFETY CLI
    • Introduction to Safety CLI Vulnerability Scanning
      • Quick Start Guide
      • Migrating from Safety CLI 2.x to Safety CLI 3.x
    • Installation and Authentication
    • Scanning for Vulnerable and Malicious Packages
      • Viewing Scan Results
      • Available Commands and Inputs
      • Scanning in CI/CD
      • Securing Development Environments
      • License Scanning
      • Exit Codes
      • Scanning in Production
    • Safety Telemetry
  • Vulnerability Remediation
    • Applying Fixes
  • Integration
    • Securing Git Repositories
      • GitHub
        • GitHub Actions
      • GitLab
      • BitBucket
      • Azure DevOps
      • Git Post-Commit Hooks
    • Pipenv
    • Docker Containers
  • Administration
    • Safety Policy Files
    • Project Policies
  • Output
    • Output Options and Recommendations
    • JSON Output
    • SBOM Output
    • HTML Output
    • Detecting Vulnerabilities and Sharing Results via Email
  • Support
    • Support
    • Invalid API Key Error
    • Headless Authentication
    • Implementation Support
    • Global proxy and identity configuration
    • Using Safety in Conda Environments
  • Miscellaneous
    • Understanding Vulnerability Scoring Systems: CVSS and EPSS
    • Release Notes
      • Breaking Changes in Safety 3
    • Research and Blog
    • Changelogs
    • Trust Center
    • Terms of Service
    • Safety 2.x Documentation
Powered by GitBook
LogoLogo

Safety Platform

  • Sign Up
  • Login

Research

  • Security Research & Blog

Resources

  • GitHub Action
  • GitHub

© Safety CLI Cybersecurity Inc.

On this page
  • Screen and text output
  • Additional Output Options

Was this helpful?

  1. Output

Output Options and Recommendations

PreviousProject PoliciesNextJSON Output

Last updated 5 months ago

Was this helpful?

Safety can output the result of a vulnerability scan to a variety of different output formats.

The default output is screen output, which prints the scan to the command line screen.

Use the --output argument to configure which output format Safety generates. The --output command line argument can be set to the following values: screen, json, html, spdx, spdx@2.2, spdx@2.3, none.

Screen and text output

--output screen (default) will print the results to the screen

Results can be easily saved to a text file. For example:

safety scan --output screen > results.txt

For more detailed output, add the --detailed-output flag

If --detailed-output is specified along with --output json then CVE details will be included in the output. In order to filter the json output to only 1 top-level key, the --filter option can be specified. For example:

safety scan --detailed-output --output json --filter cve_details

Other options that can be chosen to filter are: meta, scan_results

Additional Output Options

Full details on each output option can be found here:

  • (SPDX, SPDX@2.2, SPDX@2.3)

JSON
SBOM
HTML5