None of the AbuseFilter related software has an owner. There are a few people who have volunteered as maintainers, but in practice, most bugs are ignored unless they are fatal.
- AbuseFilter: Marius Hoch (User:Hoo man), volunteer; In-training: Legoktm, se4598, Matěj Suchánek
- AntiSpoof: Brion Vibber?, Sam Reed
- Equivset: David Barratt, Dayllan Maza
Number, severity, and age of known and confirmed security issues:
There are currently 21 open security bugs in AbuseFilter, 7 of which are high priority. AntiSpoof has 2 open security bugs.
Was it a cause of production outages or incidents? List them.
I've only listed security bugs. I don't know about other security issues related to AbuseFilter.
Does it have sufficient hardware resources for now and the near future (to take into account expected usage growth)?
Probably in it's current form, although performance has always been a concern with AbuseFilter. If we ever want to replace it with a more robust tool, it may need more hardware resources.
Is it a frequent cause of monitoring alerts that need action, and are they addressed timely and appropriately?
When it was first deployed to Wikimedia production
In the days of yore (2008?)
Usage statistics based on audience(s) served
Every edit to every WMF wiki.
Changes committed in last 1, 3, 6, and 12 months
Mostly just i18n and basic code maintenance. The biggest change in the past year was moving Equivset out of AntiSpoof and into its own library.
Reliance on outdated platforms (e.g. operating systems)
Not that I know of.
Number of developers who committed code in the last 1, 3, 6, and 12 months
Number and age of open patches
Number and age of open bugs
AbuseFilter: 311 open bugs (dating back to the Bugzilla days)
AntiSpoof: 23 open bugs
Equivset: 5 open bugs
Number of known dependencies?
AbuseFilter and AntiSpoof both depends on Equivset which depends on utfnormal.
Is there a replacement/alternative for the feature? Is there a plan for a replacement?