You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 5, 2024. It is now read-only.
Package maintainers are often busy and may end up leaving support for old packages and not updating their package.
To improve security and hopefully save time for maintainers could an automated email alert be sent to maintainers with vulnerable packages notifying them that a package they maintain is vulnerable.
I don't think I'm ever going to add email support to any of my projects, for it is an archaic, overcomplicated, insecure and unreliable service. In Repology, we also don't know maintainers for all packages, can't distinguish relevant and not relevant (e.g. groups, proxy maintainers) maintainers, and not all maintainers are in fact emails (there are fake IDs like username@aur or username@github).
There's much cleaner way which involves extending (already supported) atom feeds, and it's in fact the last item left unchecked in original issue regarding vulnerabilities support #15 - I somehow forgot that it still needs to be implemented.
I don't think #1045 is a show-stopper for this, as it's more related to resetting no longer relevant vulnerable states, while we're talking here about one-shot events which may be ignored if known to be not relevant.
@AMDmi3 Thanks for your response.
I am not sure i follow, how would atom feeds notify maintainers that their package contains a vulnerability.
Unless we are able to confirm the maintainers monitor the feeds.
Package maintainers are often busy and may end up leaving support for old packages and not updating their package.
To improve security and hopefully save time for maintainers could an automated email alert be sent to maintainers with vulnerable packages notifying them that a package they maintain is vulnerable.
This may need addressing beforehand:
repology/repology-updater#1045
The text was updated successfully, but these errors were encountered: