Our take
Activeregular commits and releases- Activity
- 58
- Community
- 38
- Issues
- 31
- Pull requests
- 63
+7 stars in the last 30 days
- Slower to close issues than 95% of the projects we track
Stepperize is an actively maintained, focused TypeScript library with useful control over state and UI, though its development is concentrated among a small number of contributors and the current v8 branch is ahead of the latest release.
Good fit if
- You are building multi-step flows in React or React Native and want typed step definitions and navigation.
- You need to own the interface, whether using the unstyled primitives or a headless import.
- You can use the MIT-licensed library and meet its React and Node.js requirements.
Look elsewhere if
- You need a prebuilt, opinionated wizard UI rather than primitives for composing your own.
- Your project does not use React or React Native.
- You require a mature, broadly distributed maintainer base: most contributions come from one person.
All health signals
| Last commit | 2026-10-16 (17 days ago) |
|---|---|
| Commits, last 90 days | 30 |
| Releases, last 12 months | 7 (latest @stepperize/react@7.0.0, 2026-06-05) |
| Contributors | 14 (top contributor: 83% of commits) |
| Issues closed, last 90 days | 3 (typically closed in 478 days) |
| Pull requests merged, last 90 days | 7 (typically merged in 0 days) |
| Project age | 2 years |
Checked on 2026-11-03 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
1,613Forks
65Change since Nov 16, 2026: 0 stars·0 forks
Overview
Stepperize is a TypeScript toolkit built for React, with bindings for React Native, for creating type-safe multi-step experiences such as wizards, forms and onboarding flows. It addresses the challenge of keeping step definitions, navigation and step-specific data consistent as a workflow grows, without prescribing a visual design.
The project offers both framework-agnostic core utilities and React bindings. Teams can use local or shared stepper state, and can build on unstyled accessible primitives or bring their own UI.
Key Features
- Define workflow steps as plain objects with typed custom fields.
- Navigate with a flat API for the current step, next and previous steps, direct navigation and reset.
- Render step-specific content with typed
matchandishelpers. - Keep step-scoped draft data and optionally validate it with per-step Standard Schema schemas.
- Track workflow completion explicitly, with navigation policies and acceptance results.
- Choose independent local state or a shared instance through a provider and selector hook.
- Use accessible, unstyled UI primitives or import the headless entry for hooks, providers, selectors and validation.
Use Cases
- A React team building a checkout flow that needs typed shipping, payment and review steps.
- Product developers creating onboarding where different steps collect distinct data and completion must be tracked.
- Teams building branching forms that need controlled navigation and optional per-step validation.
- React Native developers who want the same step-based workflow toolkit in a mobile interface.
What you need
Detected in the repository
- Node.js ^22.22.2 || ^24.15.0 || >=26.0.0 (from package.json)
- Automated checks on GitHub Actions
Getting Started
npm install @stepperize/react@^8.0.0
See the README and documentation for setup and migration details.
License in Plain Words
No standard license was detected. Without a license, the default copyright rules apply: you may read the code, but not reuse it. Check the repository or ask the authors.
Considerations
The repository is active, with regular recent commits and releases, but contributions are concentrated: most of the code comes from one person. Recent issue handling has been slow by the measured median, so teams relying on upstream support should account for that. The README identifies the current branch as preparing v8, while the latest release is v7, and points users to a v8 migration guide. The published React package supports React 18 and 19; development uses Node.js 24.18.0 and pnpm 10.28.0, while package metadata specifies supported Node.js version ranges. The project is MIT licensed.
Found this useful?
Share it with someone who would like stepperize.