Is openapi-typescript Still Actively Maintained?

[luchsamapparat]

Hi everyone,

First of all, thank you for creating and maintaining openapi-typescript. We've been using it extensively across many client projects, and it has become a key part of our toolchain. It just fits perfectly with our approach to API integration and right now we are working on an Angular adapter. In short: we love it :)

Over the past months, however, we've become increasingly concerned about the project's current status. We noticed that there hasn't been a release since February, several open pull requests remain unreviewed, and support for newer TypeScript versions (including TypeScript 6) appears to be blocked as a result.

As a consulting company working on numerous production systems, this creates growing challenges for us. We would therefore appreciate some insight into the current state and future of the project:

Is openapi-typescript still actively maintained?
Are there plans for upcoming releases and TypeScript 6 support?
Are there any blockers preventing progress?
Is there a way for the community to help, whether through code contributions, reviews, sponsorship, or additional maintainers?

We're asking not because we're looking for alternatives, but because we'd genuinely like to see the project continue to thrive. openapi-typescript has been an excellent piece of software for us, and we'd be happy to contribute in whatever way would be most helpful.

Any update on the roadmap, maintenance status, or ways the community can support the project would be highly appreciated.

Thanks again for all the work that has gone into building and maintaining this project.

[MatchuPitchu]

I would also appreciate an update on the current state.
Alternatively, can anyone recommend another project that generates OpenAPI TypeScript types of similar quality? I’m asking this as a precaution to figure out how we might proceed if the need arises.

[duncanbeevers]

Hey gang. I'm one of the maintainers on this project, and yes, it is still maintained, though my schedule has been pretty swamped lately. I'll see about allocating some time to get a few of these open PRs over the line, including TypeScript 6 support.

[michaelgiraldo]

@duncanbeevers are you looking for additional maintainers?

[doliG]

@luchsamapparat I'll be super interessed in the angular adapter, if you plan to release it in open source. Also I'd be happy to help 👍

[luchsamapparat]

Actually, we've released it three weeks ago, however we haven't used it in any production-grade project yet. So, no guarantees :)

https://www.npmjs.com/package/ngx-openapi-typescript

Feel free to check it out

[marcantoinepelletier]

Is it possible to, at least merge this one #2616 to release it ?

[prescottprue]

Also want to throw #2818 in the mix - since this tool is all about the typescript and openapi integration it would be ideal to have typescript v6 + v7 support

[darkbasic]

If someone is interested I've started maintaining my own fork with pnpm 12 for protection against supply chain attacks, vulnerability remediation, improved typescript 6 support and handling of required-only allOf constraints: https://github.com/darkbasic/openapi-typescript/commits/main/

I still don't publish any package and I still didn't make up my mind about migrating to another library or keeping maintaining this but I might at least start publishing some packages if there is enough interest and no maintainer shows up in the meantime.
For the moment feel free to build them yourself if that interests you.

[im10furry]

For everyone in this thread waiting on newer TypeScript support: TypeScript 7 support is implemented, verified, and open for review.

• feat!: generate TypeScript from string templates and drop the TypeScript dependency #2868 — TypeScript 7 support. Implements exactly what @mrlubos asked for in openapi-typescript doesn't work with Typescript 7 #2841: generate the .d.ts from raw string templates instead of the compiler API. typescript stops being a dependency and a peer dependency, so TS 5 / 6 / 7 all work and a TS7 application no longer needs a second compiler installed. Output is byte-identical to 7.13.0 for every committed example plus a differential run over 27 option combinations. 27 files, breaking, major changeset included.
• ci: stop the test-e2e job from hanging for 6 hours #2869 — CI fix, independent and 2 files. test-e2e has been dying inside playwright install --with-deps at GitHub's 6-hour job limit on every run since 2026-08-24 — the last green e2e was 79s that day, and the job has never reached the tests since. It's green again in 57s. Landing this one first also turns feat!: generate TypeScript from string templates and drop the TypeScript dependency #2868's e2e green, because feat!: generate TypeScript from string templates and drop the TypeScript dependency #2868 doesn't touch the workflow file.

Both are green and ready; the only open question I'd like a maintainer's call on is the transformProperty hook shape (there's a comment on #2868 with the detail and two alternatives). Everything else is a mechanical migration for callers — CLI users and consumers of the generated types need no changes at all.

For context, the two TS7 blockers were:

npm error peer typescript@"^5.x" from openapi-typescript@7.13.0     # blocks install outright
TypeError: Cannot read properties of undefined (reading 'createKeywordTypeNode')   # blocks a forced install

@duncanbeevers — you said earlier in this thread that you'd try to get some of the open PRs over the line. If you have a moment, #2869 is the cheapest possible win for the repo: two files, CI-only, and it unblocks the e2e job for every PR here rather than just this one. @mrlubos — you defined the approach in #2841, so #2868 is the shape you asked for, and I'm happy to change the hook signature to whatever you'd prefer.

I'm not attached to any of the implementation choices; I'd just rather this not sit behind an unstaffed queue given how many people in this thread are waiting on it.

[darkbasic]

Thanks @im10furry I've used your PR as a base to add support for TS7 in my branch alongside TS6. I've extracted a PR from my fork if it may be useful to anybody: #2872