tegioz
commented
3 weeks ago Hi @caniszczyk
We already have something similar to this in CLOMonitor 🙂
https://clomonitor.io/data/repositories.csv
(this file can be downloaded from the stats page in CLOMonitor -screenshot attached below-)
The main difference is that, even though all entries specify the corresponding project, the data is classified per repository. The reason it works this way is that this data includes the results of all checks, and they can vary from repository to repository within the same project (i.e. one of the project's repos may pass the DCO check, but other may not).
If this is a problem and you prefer to have a dump with an entry per project, we'd just need to agree on the criteria to summarize the checks across multiple repositories in a single entry for a project.
Some would be straightforward, like the website or roadmap checks, but many others are repository specific and depending on the criteria used the result may be misleading. Some examples would be the license approved or the dangerous workflow checks (there are quite a few more). Should we consider the check passed across the project if it passes in all the project's repositories? In any of them?
It would be good if we can get a CSV dump or sheet view of all the filtered data in clomonitor
This is related to:
https://github.com/cncf/landscape2/issues/659