autoform's core is agnostic and its adapters are not
🌟 Automatically render forms for your existing data schema
At a glance
- What is it?
- A React form renderer that takes a schema you already have and maps it onto inputs, where the core is agnostic and the adapters are named after the UI library and form library they combine, the root package is private, and releases go out through changesets with no GitHub release behind them.
- Who is it for?
- autoform is a good fit when you already hold a Zod, Yup or Joi schema for a backend and want an internal admin form out of it without hand wiring fields, because that is the case the page describes and the shape the code takes. Two things to weigh.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 17 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- vantezzen/autoform3,494 ★ · +0
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| vantezzen/autoform | 3.5k | 3.5k |
0 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The scope is stated twice, and both times it is narrow
The positioning paragraph is unambiguous. AutoForm is mostly meant as a drop-in form builder for your internal tools and simple forms with existing schemas, with the worked example being schemas you already have for your API turned into a simple admin panel for editing user profiles. Then the caveat arrives: AutoForm does not aim to be a full-featured form builder or support every edge case in your schema. What it claims instead is that it does not change how you write custom inputs or access data, state and methods, and that you still use your form library the way you usually would. That sentence has a missing space in it, would and Rather run together, which is a small thing but it sits in the middle of the paragraph carrying the project's main claim about itself.
The core is agnostic and the adapters are named for two libraries
The split is announced in one line: AutoForm itself is agnostic to the schema, rendering and UI library you use. The adapters are where the choices live, and the import paths show how they are named. A schema goes through a provider, `import { ZodProvider } from "@autoform/zod"`, and a form comes from a package that names the UI library and the form library together, `import { AutoForm } from "@autoform/mui/react-hook-form"`. The UI libraries named as having official packages are Material UI, shadcn/ui, Mantine, Ant Design and Chakra UI. The validation libraries are Zod, Yup and Joi. Two getting started guides are offered, one for React Hook Form and one for TanStack Form, so the adapter axis that matters in practice is the form library.
The example carries one prop beyond schema and onSubmit
The whole render call is three props.
import { AutoForm } from "@autoform/mui/react-hook-form";
// shadcn CLI install: "@/components/ui/autoform/react-hook-form"
import { schemaProvider } from "./schema";
function MyForm() {
return (
<AutoForm
schema={schemaProvider}
onSubmit={(data) => {
console.log(data);
}}
withSubmit
/>
);
}Only `withSubmit` is not obvious, and its presence is what turns the component from a set of fields into something with a submit button. The comment on the second line is a second install route for shadcn users, a component path for the shadcn CLI alongside the package import. Behind it the schema is ordinary Zod, a string, a coerced date and an email, wrapped once in `new ZodProvider(userSchema)` and exported as a single `schemaProvider` value.
The escape hatches are a config option and your own renderer
Two levels of customization are offered, and the page is clear that using them means leaving the drop-in path. The first is a `fieldConfig` option for customizing how forms are rendered. The second is customizing AutoForm's renderer inside your own project, linked to an anchor named customizing the react package. The example given for what that looks like in practice is not in this repository: it points at AutoForm YAML, a project by a different author, for YAML based, multi-page forms, described as more powerful. So the official answer to a complex case is a fork of the render layer, and the reference implementation of that lives somewhere else.
Two repository names for one project
The page accounts for its own history in a single sentence: AutoForm evolved from a shadcn/ui component into a standalone library with broader UI and schema support. The link behind that sentence goes to `vantezzen/auto-form`, with a hyphen, while the repository you are reading is `vantezzen/autoform`, without one. That is the whole story, and it matters for anyone following a link from an older thread or an earlier answer, because the hyphenated name is the component and the unhyphenated one is the library. The package scope is different from both, since the published packages sit under the `@autoform/` scope.
Releases go through changesets, which is why there are no GitHub releases
The repository has no GitHub releases, and the tooling says where versions come from instead. There is a `.changeset/` directory at the root and `@changesets/cli` as the single runtime dependency of the root package. The release sequence is three commands.
pnpm changeset version
pnpm changeset publishRecording a change is a separate step, `pnpm changeset`, and the page frames that as how you document a change rather than how you build one. So a version here is an npm publication produced by a bot from a changeset file, and the GitHub releases list stays empty by design of the workflow rather than by neglect.
The os and cpu fields sit on the package that is never published
The root manifest is marked `"private": true`, which means it is never installed by anyone, and the `os` and `cpu` arrays sit on that root: `darwin`, `linux` and `win32` for the first, `x64` and `arm64` for the second. Whether that is deliberate or simply where the fields were added, the effect is that the restriction travels with the workspace root and not with any `@autoform/` package a consumer installs. Two more version facts sit alongside. `engines` asks for node `>=18` and pnpm `>=9.0.0`, while `packageManager` pins `[email protected]`, a much narrower range than the one being asked for. And there is a `.nvmrc` plus an `.npmrc` at the root for the toolchain to pick up.
A monorepo with a custom boundary checker and one test workspace
The tree is a TurboRepo monorepo: `apps/`, `packages/`, `scripts/`, `turbo.json`, `pnpm-workspace.yaml`, a `registry.json` and a `skills/` directory. Setup is two commands, `pnpm install` and `pnpm dev`, and the dev server starts the documentation website as well as the package itself, with the pipeline capped at `turbo dev --concurrency 20`. Release checks add a step with no equivalent elsewhere: `check:packages` runs `node scripts/check-package-boundaries.mjs`, a bespoke script whose job is to keep the packages from reaching across into each other. The Cypress scripts are filtered to a single workspace, `turbo run cypress --filter=web`, so component tests belong to the web app and not to the packages.
Editorial conclusion
autoform is a good fit when you already hold a Zod, Yup or Joi schema for a backend and want an internal admin form out of it without hand wiring fields, because that is the case the page describes and the shape the code takes. Two things to weigh. The project is explicit that it is not a full featured form builder and does not aim to cover every edge case in your schema, so anything complicated is meant to be handled by customizing its renderer inside your own project. And there is no GitHub release to pin, since versions are cut with changesets and published to npm, so a version range in your own dependencies is the only anchor there is.
Frequently asked questions
how to use autoform
Wrap an existing schema in a provider, for example new ZodProvider(userSchema), export it, and pass it to the AutoForm component as the schema prop along with an onSubmit handler. The component package you import depends on your UI library and form library, for example @autoform/mui/react-hook-form.
how to install autoform
There is no single install command for consumers; you add the provider package and the component package for your stack, both under the @autoform scope. For working on AutoForm itself, it is a pnpm monorepo: run pnpm install and then pnpm dev, which starts the documentation site and the package.
Which UI and validation libraries does AutoForm support?
Official packages are named for Material UI, shadcn/ui, Mantine, Ant Design and Chakra UI on the UI side, and Zod, Yup and Joi on the validation side. Two getting started guides are offered, one for React Hook Form and one for TanStack Form. The core is agnostic to the schema, rendering and UI library you use.
Can AutoForm handle a multi-page or YAML-driven form?
Not out of the box. The page states that AutoForm does not aim to be a full-featured form builder or support every edge case in your schema, and points to customizing the renderer in your own project. For a YAML based, multi-page form it points at a separate project by another author called AutoForm YAML.
How do I develop AutoForm locally?
It is a TurboRepo monorepo. Run pnpm install and pnpm dev for the development server, which starts the documentation website and the package together. Release checks are pnpm build, pnpm check:packages and pnpm cypress, and pnpm cypress:open opens the component tests in the Cypress UI.
How does AutoForm publish a release?
Through changesets. You record one with pnpm changeset, and publishing runs pnpm changeset version followed by pnpm changeset publish, with @changesets/cli as the root package dependency and a .changeset directory in the tree. The repository itself has no GitHub releases.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/vantezzen-autoform)Star history chart for your README
[](https://hysenlabs.com/projects/vantezzen-autoform)Was this useful?