Measures the number of major, minor, and patch versions between your dependencies' installed and newest versions

[nasirhjafri]

Add a new argument --versions to measures the number of major, minor, and patch versions between your dependencies' installed and newest versions

$ libyear --versions
                 activesupport        4.2.7.1     2016-08-10          5.1.3     2017-08-03      [1, 0, 0]
                          i18n          0.8.0     2017-01-31          0.8.6     2017-07-10      [0, 0, 6]
                          json          1.8.6     2017-01-13          2.1.0     2017-04-18      [1, 0, 0]
                      minitest         5.10.1     2016-12-02         5.10.3     2017-07-21      [0, 0, 2]
             minitest_to_rspec          0.6.0     2015-06-09          0.8.0     2017-01-02      [0, 2, 0]
                   ruby_parser          3.8.4     2017-01-13         3.10.1     2017-07-21      [0, 2, 0]
                sexp_processor          4.8.0     2017-02-01         4.10.0     2017-07-17      [0, 2, 0]
                   thread_safe          0.3.5     2015-03-11          0.3.6     2017-02-22      [0, 0, 1]
                        tzinfo          1.2.2     2014-08-08          1.2.3     2017-03-25      [0, 0, 1]
Major, minor, patch versions behind: 2, 6, 10

[miketheman]

This assumes that packages adhere to SemVer, correct? Python packages often adhere to it, but even PEP440 doesn't require the full version X.Y.Z.

How would you consider reporting on packages that don't adhere to the spec?

(same question applies to #11 )