Skip to main content

bdvr, an Customized Blackduck_Vulnerability_report

Use case:

Project stakeholders want to know which files are affected with vulnerabilities after a Blackduck HUB scan.

Drawbacks:

The current blackduck generates multiple reports. To fulfill above requirement once has to refer 2 different reports to really able to trace the source files affected.

Features

  1. Produces customized report where we can see vulnerability, OSS name, affected source path details all in one report

  2. Color coded

    low risk = no color

    medium risk = Yellow

    High risk = Red

  3. Omits all other files which has no vulnerabilities.

Prerequiites:

Export your environment variable (in linux)

export BD_URL="https://www.your_blackduck.com" && export BD_TOKEN="YOUR_API_TOKEN"

How to install

pip install bdvr

Command to run

bdvr -h
usage: A program to create vulnerability reports for a given project-version [-h] [-z ZIP_FILE_NAME] [-r REPORTS] [--format {CSV}] [-t TRIES] [-s SLEEP_TIME] [--no-verify]
                                                                             [-o]
                                                                             project_name version_name

positional arguments:
  project_name
  version_name

options:
  -h, --help            show this help message and exit
  -z ZIP_FILE_NAME, --zip_file_name ZIP_FILE_NAME
  -r REPORTS, --reports REPORTS
                        Comma separated list (no spaces) of the reports to generate - ['version', 'scans', 'components', 'vulnerabilities', 'source', 'cryptography',
                        'license_terms', 'component_additional_fields', 'project_version_additional_fields', 'vulnerability_matches', 'upgrade_guidance',
                        'license_conflicts']. Default is all reports.
  --format {CSV}        Report format - only CSV available for now
  -t TRIES, --tries TRIES
                        How many times to retry downloading the report, i.e. wait for the report to be generated
  -s SLEEP_TIME, --sleep_time SLEEP_TIME
                        The amount of time to sleep in-between (re-)tries to download the report
  --no-verify           disable TLS certificate verification
  -o                    (Optional) To automatically open the file

#To automatically open the file add -o option
bdvr BD_PROJECT_NAME BD_PROJECT_VERSION

Dependenceis

Thanks to all authors. As this library uses below modules
pandas = "^1.4.3"
quo = "^2022.8.2"
universal-startfile = "^0.1.3"

Issues

Please send your bugs to dineshr93@gmail.com

License

MIT

Metadata

Release files for bdvr 0.12.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for bdvr 0.12.0
File Size Uploaded Provenance Actions
bdvr-0.12.0.tar.gz 7.1 kB Without provenance Details for bdvr-0.12.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for bdvr 0.12.0
File Interpreter ABI Platform Actions
bdvr-0.12.0-py3-none-any.whl Python 3 none any Details for bdvr-0.12.0-py3-none-any.whl

Total release size: 14.3 kB

Release files / bdvr-0.12.0.tar.gz

Download URL bdvr-0.12.0.tar.gz
Size 7.1 kB
Tags Source
SHA-256 checksum
How to use checksums
3315dd35f33c980164c670924b4737cbeebdc9a3135c332ec5fbef97131ec376
BLAKE2b-256 checksum
How to use checksums
b4ac5444b0365cf92647bf48d9484fb0396be2419565f45115647f457536515f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.0.0 CPython/3.10.12

Release files / bdvr-0.12.0-py3-none-any.whl

Download URL bdvr-0.12.0-py3-none-any.whl
Size 7.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6fd74f1004d15deaa5e5eb5660f2e96491762a3259964cf5de624e3f3665600d
BLAKE2b-256 checksum
How to use checksums
dfee507c66b8f2e58d21d554a3b11792c0c9657b5e832d1aa143fd17860f6c62
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.0.0 CPython/3.10.12

Security for bdvr 0.12.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page