vantezzen/autoform

🌟 Automatically render forms for your existing data schema

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 43 minutes ago
Added to GitGenius on September 19th, 2026
Created on July 21st, 2023
Open Issues & Pull Requests: 18 (+0)
GitHub issues: Enabled
Number of forks: 148
Total Stargazers: 3,494 (+0)
Total Subscribers: 15 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 15
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 575 days
Stale 30+ days: 15
Stale 90+ days: 14

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • help wanted (2)
  • contributions welcome (1)
  • good first issue (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

AutoForm is a React component library that automatically renders forms from existing data schemas.

The tool solves the problem of repetitive form boilerplate by mapping schema fields directly to input components and wiring up validation automatically. It works by accepting a schema (from Zod, Yup, Joi, or other validation libraries) and generating a complete form without manual field binding. The approach keeps the underlying form library and schema validation intact, so developers continue using their chosen tools in their normal way while AutoForm handles the mechanical wiring between schema and UI.

AutoForm suits internal tools, admin panels, and straightforward forms where a schema already exists for backend validation. It works with popular UI libraries including Material UI, shadcn/ui, Mantine, Ant Design, and Chakra UI, and supports multiple form libraries such as React Hook Form and TanStack Form. The tool is not intended as a full-featured form builder for complex, highly customized forms; it provides escape hatches through field configuration and renderer customization for cases that outgrow its defaults, but developers needing extensive customization should consider building on top of it or using alternatives designed for that purpose.

The project uses a TurboRepo monorepo structure and maintains a documented changelog through changesets. Development includes component testing via Cypress and a documentation website that runs alongside the package during local development. The codebase is written in TypeScript.