Add entryPath parameter to XML-3, XML-4 and POL-9

[maria-messerschmidt]

The JSON output for XML-3, XML-4 and POL-9 are missing the entryPath parameter even though they relate to individual zip entries and should have this parameter. Would it be possible to add it?

Let me know if you need example files to test :)

{
"message" : {
"id" : "XML-3",
"severity" : "ERROR",
"title" : "Not a well formed XML document. XML parsing exception at line 1 and column 1: Content is not allowed in prolog..",
"parameters" : [ {
"name" : "line",
"value" : "1"
}, {
"name" : "column",
"value" : "1"
}, {
"name" : "message",
"value" : "Content is not allowed in prolog."
} ],
"timestamp" : "2025-07-20 08:35 UTC",
"text" : ""
},
"path" : "META-INF/parse"
}

{
"message" : {
"id" : "XML-4",
"severity" : "ERROR",
"title" : "Not a valid XML document. Validation exception at line 32 and column 55: attribute "style:hopla" not allowed here; expected attribute "style:font-adornments", "style:font-charset", "style:font-family-generic", "style:font-pitch", "style:name", "svg:accent-height", "svg:alphabetic", "svg:ascent", "svg:bbox", "svg:cap-height", "svg:descent", "svg:font-family", "svg:font-size", "svg:font-stretch", "svg:font-style", "svg:font-variant", "svg:font-weight", "svg:hanging", "svg:ideographic", "svg:mathematical", "svg:overline-position", "svg:overline-thickness", "svg:panose-1", "svg:slope", "svg:stemh", "svg:stemv", "svg:strikethrough-position", "svg:strikethrough-thickness", "svg:underline-position", "svg:underline-thickness", "svg:unicode-range", "svg:units-per-em", "svg:v-alphabetic", "svg:v-hanging", "svg:v-ideographic", "svg:v-mathematical", "svg:widths" or "svg:x-height".",
"parameters" : [ {
"name" : "line",
"value" : "32"
}, {
"name" : "column",
"value" : "55"
}, {
"name" : "message",
"value" : "attribute "style:hopla" not allowed here; expected attribute "style:font-adornments", "style:font-charset", "style:font-family-generic", "style:font-pitch", "style:name", "svg:accent-height", "svg:alphabetic", "svg:ascent", "svg:bbox", "svg:cap-height", "svg:descent", "svg:font-family", "svg:font-size", "svg:font-stretch", "svg:font-style", "svg:font-variant", "svg:font-weight", "svg:hanging", "svg:ideographic", "svg:mathematical", "svg:overline-position", "svg:overline-thickness", "svg:panose-1", "svg:slope", "svg:stemh", "svg:stemv", "svg:strikethrough-position", "svg:strikethrough-thickness", "svg:underline-position", "svg:underline-thickness", "svg:unicode-range", "svg:units-per-em", "svg:v-alphabetic", "svg:v-hanging", "svg:v-ideographic", "svg:v-mathematical", "svg:widths" or "svg:x-height""
} ],
"timestamp" : "2025-07-20 08:35 UTC",
"text" : ""
},
"path" : "META-INF/schema"
}

{
"message" : {
"id" : "POL-9",
"severity" : "ERROR",
"title" : "Digital Signatures",
"parameters" : [ ],
"timestamp" : "2025-07-20 08:35 UTC",
"text" : "The package MUST NOT contain any digital signatures."
},
"path" : "META-INF/signatures"
}

[carlwilson]

Hi @maria-messerschmidt, I don't think that will be a problem. I'll look to add this ASAP.

[carlwilson]

I've had a look, and initially, my attempts to implement this are messy. The problem is that I don't really want low-level validators worrying about things they don't need to, e.g. the file/path name, or whether it's a file at all. This means threading information through. All the messages have a "path" key that shows which file they were triggered for, could that be used. If not, we may want to chat about this some.