Rationalising presentation of data on dependencies, packages, and 'projects' #187
Description
Dependencies, packages, and projects are all strongly tied together. I wonder whether we should only ever use the 'project' to show data about any of these things, as there is little of interest otherwise.
For instance:
This list shows all the dependencies, which is useful for a security analysis, but possibly less so for a dashboard
This basically shows the latest versions of packages published by aslant, which is useful for some research, but possibly less so for a dashboard: https://dashboard.ecosyste.ms/projects/51/packages?
my proposal is that, whenever we're showing data like this we show the single most important piece of information about that object (the dependency version, the latest package release) and the information about the project, which you can then click through to.