Project

myprecious

0.0
No release in over 3 years
Low commit activity in last 3 years
A simple, markdown generated with information about your gems and python packages
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 1.13
>= 0
~> 0.13

Runtime

>= 1.0.0, ~> 1.0
>= 1.5.0, ~> 1.5
~> 2.0
>= 2.0, ~> 2.0.2
~> 2.3
 Project Readme

myprecious

Generate a Markdown report with information about your dependencies

Supports

  • Ruby Gems
  • Python Packages

Command Line Help

myprecious help

Configuration

CVE Vendor Blocking

Because the search for CVEs in NIST's NVD can turn up false-positive matches, especially for dependencies with generic names like "mail", myprecious can be configured to ignore CVEs whose CPEs identify particular vendor/product pairs. To do this, a file named .myprecious-cves.rb must be put in the same directory as the target project's package configuration (either the current directory or specified with the -C/--dir option). That file must be a Ruby file that outputs JSON to STDOUT. An example would be:

require 'json'

JSON.dump({
  blockedProducts: %w[
    apple:mail
    basercms:mail
    downline_goldmine:builder
  ],
}, $stdout)

Each entry in blockedProducts should be a vendor:product pair, just as it would appear in the irrelevant CPE(s).

Installing bash completions

Run the myprecious executable file with the --install-completions flag. It will both install completions for bash session launched in the future and provide the path to the bash script that can be sourceed in any existing bash sessions to enable completion. This command only needs to be run once.