StaffThanks for the clarification.
So looking on Maven
https://mvnrepository.com/artifact/io.swagger/swagger-compat-spec-parser/versions
This would be the 1.x line of the swagger-parser repo
https://github.com/swagger-api/swagger-parser/tree/v1
The traditional path would be remediating the vulns at source, with a contribution to jackson-coreutils, which consuming libraries such as swagger-compat-spec-parser can pull in via a corresponding pull request targeting the v1 branch.
> I would also appreciate guidance on whether Swagger 1.2 compatibility still has a supported migration path.
I do not know of any other than migrate to a newer version of Swagger now OpenAPI specification, especially as the swagger ecosystem rolls out Jackson 3, I don't believe you'll be able to support Jackson 2/3 in the same project.
Could I be nosy and ask the use case for supporting Swagger 1.2? I joined the ecosystem at Swagger 2.0 back in early 2015 and have never used 1.2!
