Is this project still actively maintained?

[lamuertepeluda]

Hi there,

I was willing to fork and create a PR for #303, so I forked and followed the instructions from CONTRIBUTING.md.

In short, tests do not pass . And there are toolchain issues, beside dependencies issues as in #303.

However

• Using Node 20 and Yarn 4 the lib does not build and yarn messes up the project structure
• Using Node 20 or 18 and Yarn 1.22 the lib does not build and 15 tests do not pass but at least yarn does not add problems to problems
• Using Node 16 and Yarn 1.22 (should be stated clearly somewhere, maybe in the packag.json "engines") it bulds, but 15 tests still do not pass (see screenshot).

So I wonder: is this package/set of packages still maintained?

[ehuelsmann]

@lamuertepeluda, I forked and updated all these dependencies and test fixes. See ehuelsmann/OpenAPIValidators, which is available on NPM as @ehuelsmann/OpenAPIValidators. Given the lack of response to your question, which you asked more than a year ago, I felt the fork was warranted.

[lamuertepeluda]

Thanks @ehuelsmann. Since this project seems definitely dead ☠️ or unmaintained, but thanks God OAS isn't, I had to resolve to a custom Jest validator to manage some OAS syntax that is not handled here, as well as snyk/audit issues.

My implementation (not a lib) exploits:

• https://github.com/seriousme/openapi-schema-validator for OAS spec document validation
• https://www.npmjs.com/package/openapi-backend to validate requests in my jest tests

I've also added the same approach in another project where I try to get rid of jest in favor of node:test with Node 24

I will gladly have a look at your fork, though!