Please add a rule for iText

[Vampire]

iText itself was published under three coordinates and additionally there is a fork from the last non-AGPL version that is actively maintained but started to count the version from 1.0.

There is "original" coordinates:

itext:itext

• current version 1.3.1 released on 2006-03-27
• package com.lowagie.text and others
• GNU Lesser General Public License (LGPL), Version 2.1
• Mozilla Public License Version 2.0

com.lowagie:itext <=2.1.7

• current version 2.1.7 released on 2009-07-09
• package com.lowagie.text and others
• GNU Lesser General Public License (LGPL), Version 2.1
• Mozilla Public License Version 2.0

com.lowagie:itext >2.1.7

• current version 4.2.2 released on 2015-07-10 which has a jar but also a relocation to com.itextpdf:itextpdf
• package com.lowagie.text and others
• GNU Affero General Public License v3

com.itextpdf:itextpdf

• current version 5.5.13 released on 2018-01-26
• package com.itextpdf
• GNU Affero General Public License v3

And then there is the actively maintained fork that was created from last non-AGPL release but started with version 1.0:

com.github.librepdf:openpdf

• current version 1.3.39 released on 2024-01-19
• package com.lowagie.text and others
• GNU Lesser General Public License (LGPL), Version 2.1
• Mozilla Public License Version 2.0

I'm not sure how to model this properly, but I hope the information I provided allow you to shape up senseful rules. I guess com.itextpdf:itextpdf as it also changed the package naming should maybe not be considered but kept separately, but the others all providing the same capability. But even then I'm not sure what makes most sense for a default resolution strategy or if there is one that makes more sense than the other.