Expose Dependency version age as package metadata

Summary

Some organizations are interested in understanding the age of a dependency version.

This helps them ensure that they are staying up to date with their dependencies. Additionally, some users may want to build a policy around dependency age. This policy could prevent dependencies of a certain age from being permissible for use within their codebase.

Some organizations want to keep dependencies up-to-date, while others want to prevent developers from introducing dependencies that are too newly released (e.g., young).

Proposal

Show age of Dependency in API (MVC).

Post MVC we should show this information in the GitLab UI.

Intended users

Personas are described at https://about.gitlab.com/handbook/product/personas/

• Delaney (Development Team Lead)
• Amy (Application Security Engineer)
• Alex (Security Operations Engineer)
• Cameron (Compliance Manager)