New VersionDistance policy to check and report outdated components

[walterdeboer]

Current Behavior

Dependenct Track now supports a Component Age Policy and a Component Version Policy, but both are unsuitable to detect outdated components. For this the distance between the current component version and it's latest version needs to be analysed.

Proposed Behavior

The Version Distance is specified as the numerical distance between the two epoch numbers, two major numbers, the two minor numbers and the two patch numbers, e.g:
0:1.0.0 = same epoch, 1 major version distance, dont know about minor or patch
0:0.1.0 = same epoch, same major, 1 minor version distance, dont know about patch

Add a Policy to evaluates the VersionDistance between a Component's current and it's latest (stable) version. The policy "greater than 0:1.0.0" for example, means a difference of only one between the current version's major number and the latest version's major number is allowed.

Checklist

• I have read and understand the contributing guidelines
• I have checked the existing issues for whether this enhancement was already requested

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.