3neti/form-flow

This release appears suitable to depend on, with strong evidence of active maintenance and good project hygiene: 51 stable releases in about 252 days, recent repository activity, tests, changelog, documentation, an MIT license, a security policy, and a repository that clearly matches the package. The main concerns are the very small user-facing footprint, a two-contributor repository with 90.6% of recent commits from one contributor, and the absence of repository security-scanning tools; these increase continuity and assurance risk but do not outweigh the package's recent activity and substantial scaffolding.

Latest v1.9.25

Packagist

83%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

100

Health Score Breakdown

Maintainers

Only one account has registry publish access, which creates publishing continuity risk. However, the linked repository shows two active maintainers, so this is a caution rather than a severe health issue.

Project backing

The repository is owned by a user rather than an organization, so there is no organization-level maintenance handoff signal. This makes the observed contributor concentration more relevant, although recent activity remains strong.

Repo bus factor

Recent work is concentrated in two contributors, with the top contributor responsible for 90.625% of commits. The second contributor remains active, but the high concentration leaves a meaningful continuity risk for this user-owned project.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This is not inherently negative for a small package, but it provides little evidence of an active user community.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is supporting evidence rather than a verdict, but these values provide no external adoption signal and modestly reduce confidence in maturity.