Clarification on Project Activity and Maintenance Status

[aliuygur]

Hi there 👋

We are considering adopting AdminJS in a new project, but before doing so we’d like some clarification on the current maintenance status of the project.

From what we’ve observed so far:

• The last significant commit and release activity appears to be around mid-2025. :contentReference[oaicite:0]{index=0}
• There are many open issues and PRs with limited visible progress in recent months. :contentReference[oaicite:1]{index=1}
• Various sources (e.g. package health reports) suggest the overall maintenance activity may be low or inactive recently. :contentReference[oaicite:2]{index=2}

Could you please clarify:

1. Whether the project is still actively maintained?
2. If there is a preferred branch/location where ongoing development happens (e.g., a monorepo like adminjs-dev)?
3. Whether there are any plans for future releases or feature updates?
4. How the maintainers recommend handling outstanding issues/PRs?

Thanks in advance for the help! 🙏

— A potential user evaluating AdminJS

[TheYangYang]

I believe it is dead

[mp-blurify]

I think it's only for their internal use in projects, but without any press on fixing and maintaining. Types in whole project are any or Record<string, any> - without generic pattern, very huge pain for developing with type-safety.

[johnsnowdies]

Are there any active forks? The current version contains a lot of security vulnerabilities, most critically in adminjs/relations. I'd be glad to contribute, but it looks like the repository is abandoned.

[rulab]

Hi. The project hasn't really been updated much in the last year, although I still consider it production-ready and use it in many projects. Where standard features aren't available, I write my own plugins using the features API and am ready to share them with the community https://github.com/rulab/adminjs-components

[ivictbor]

Are there any active forks? The current version contains a lot of security vulnerabilities, most critically in adminjs/relations. I'd be glad to contribute, but it looks like the repository is abandoned.

We actively maintain https://adminforth.dev it is not a fork, but a very similar TypeScript admin framework. There are many plugins, such as a Bulk AI handling plugin (image→text, text→image, image→image), different SSO plugins, audit log, batch jobs, and many more.

We are a software development team and built it for ourselves to provide our clients with more value and to deliver various back offices very quickly, with the ability to extend any part very easily when all the basic functionality is already in place. So we are going to maintain it as long as our company exists 😉

Also, as you can see from closed issues on github, we are open to community proposals at any time.

[KaKi87]

Hi,

I'm looking for an AdminJS alternative too. Did anyone find any ?

Seems like https://github.com/kottster/kottster invested a lot in advertising given how that's the only search result I get, but even that one hasn't been maintained in the last 3 months.

We actively maintain https://adminforth.dev/ it is not a fork, but a very similar TypeScript admin framework

Can it not work with anything else than Prisma ORM ?

It's weirdly mentioned in the README and docs as if it was natural an obvious that I would be using that, without saying whether it's a requirement and whether it's the only choice.

[ivictbor]

Can it not work with anything else than Prisma ORM ?

AdminForth works without Prisma ORM and without any migration tools or ORMs. Moreover AdminForth does not manage schema at all - you mange it in any way you wish - SQLAlchemey, Prisma, any other migration tool or manual SQL creation.
So you should create DB by yourself - then simply create one resource (one file) per table and one column for every column which you want adminforth to be aware about. Of course instead of manual management just use CLI npx adminforth resource - and it will create resource or import updates for you.

Prisma only shipped in basic template as an example tool to manage schema, to quickly start for developer with low expertise, but if you will remove it from project - everything will work in the same way.

Currently next DBs are supported:

• MySQL
• Postgres
• MongoDB
• Clickhouse
• SQLite
• QDrant

But you can very quickly create own data connector by extending exposed Interface for another databases, or proxy data operations to your APIs if you need really deep level of control