Dmitry Marakasov
Dmitry Marakasov
Add events if some repo has rolled latest version back. Example where this would make history more consistent: https://repology.org/project/podman/history - there's some problem in homebrew visible here as podman is...
Example: https://repology.org/project/packit/versions Not sure whether these need to be fixed in the updater on in the webapp.
Mark vulnerable package versions The plan: - [x] Implement harvesting CPE data from upstream repositories - :x: GUIX contains `cpe_name` (is useless without vendor) - :x: FreeBSD ports define CPE_VENDOR...
Doesn't look like it's worth spending time on right now, but as an idea for future: - jenkins plugins - https://repology.org/projects/?search=jenkins%25plugin - many vulnerable in the past - official catalogue:...
Somewhere in #956 we've lost ability to update projects (or, more precisely, problems) when link statuses change. This needs to be fixed, although it's quite complex - we need to...
Currently we have to use magic numbers like `(1
Add custom hooks which are run before/after repository fetch/parse, so we can, for example, keep history of raw repository state for debugging.
E.g. `Void Linux x86_64` and `OpenWrt 19.07 x86_64` should not contain arch in their name as we do not differentiate repositories by arch (there should be other mechanism to explore...
Whitespace in an URL currently emits warning to the log, because it may mean that a particular string we parse URL from contains multiple URLs instead. However in most cases...