zoclee/flux

This is a very new, actively developed MVP release with strong basic packaging evidence, an MIT license, a changelog, repository tests, no install-time scripts, no deprecation, and recent repository activity. However, the package is only 16 days old, remains below a stable major release, has rapid early release churn, and all 71 recent commits come from one contributor; organization ownership partly mitigates the bus-factor concern but does not eliminate it. The linked repository also does not match the package name or mention it in its README, creating a meaningful provenance and package-identity concern that should be resolved before relying on it for critical infrastructure.

Latest v0.2.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Six releases in only 16 days show active iteration, but the package has very limited historical maturity and the roughly 23-hour median release interval indicates an unsettled early development phase.

Repo bus factor

All 71 recent commits came from one contributor, creating a genuine concentration and continuity risk. Organization ownership provides some ability to hand off maintenance, but no second active contributor is evidenced.

Repo issue activity

There are no open issues or pull requests and no recent issue or PR activity; this is neutral for a new project but provides little evidence of an established user or maintainer feedback loop.

Repo package mention

The linked repository name does not match the package name, and its README does not mention the package. Because this package appears to be published as zoclee/flux while the repository is Zoclee/fluxq, the relationship and provenance should be verified before adoption.

Repo popularity

The repository has only 1 star, 0 forks, and 0 watchers. This is weak supporting evidence, but low popularity alone is not a health verdict for a young package.