tomasvotruba/fast-unit

This is a usable but very young package with strong basic transparency: it has an MIT license, a matching source repository, active recent releases and commits, no deprecation, and no observed dangerous workflow patterns or install-time scripts. The main concerns are its 22-day age, pre-1.0 version, single-maintainer and single-contributor bus factor, absence of repository tests and security scanning, and incomplete workflow permission declarations. The package appears actively developed rather than abandoned, but its limited history and concentrated maintenance make it a dependency that warrants monitoring and cautious adoption.

Latest v0.1.6

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

There is one registry maintainer, Tomas Votruba. Because the linked project is user-owned rather than organization-owned, this reflects a genuinely narrow publishing base, though repository activity provides evidence that the maintainer is active.

Package scaffolding

A substantial README documents installation, usage, and binary rebuilding, and the repository uses GitHub Releases; however, neither the artifact nor repository contains tests or a changelog. The documentation and release evidence partly compensate for the missing changelog, but the lack of tests remains a maintenance-quality gap.

Project backing

The source repository is owned by the individual user TomasVotruba rather than an organization. This provides a clear owner but no organizational maintenance redundancy, consistent with the single-contributor risk.

Release history

The package is only 22 days old, although it has already had 7 releases and the latest release was published recently. The rapid release activity is encouraging but provides little long-term evidence of maintenance stability.

Repo bus factor

All 5 recent commits came from one contributor, giving the project a complete single-contributor concentration. With a user-owned repository and no second active contributor, loss of that maintainer would materially increase abandonment risk.