simsoft/data-flow

This is a generally healthy and usable release: it is a stable major version, not deprecated, has a 648-day history with 20 releases including 8 in the last 12 months, and the linked repository is active, unarchived, and clearly matches the package. The artifact and repository provide substantial documentation, changelog, licensing, CI, and test evidence, with a small runtime dependency footprint and read-only workflow permissions. The main concerns are that recent commit activity is limited to 1 commit by a single contributor, the repository has no security policy or security-scanning tooling, and the project has negligible measured popularity; these increase maintenance and transparency risk but do not outweigh the strong release and repository evidence.

Latest 3.1.1

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by the user account sim-soft rather than an organization, so there is no organizational backing signal to compensate for the thin recent contributor base.

Repo bus factor

All recent commits came from one contributor, creating a concentrated maintenance dependency; the repository owner is a user rather than an organization, so there is no provided organizational backing to offset this concentration.

Repo commit activity

Only 1 commit was recorded in the last 3 months from 1 active maintainer, indicating a recent slowdown despite the package's strong release cadence and current repository push.

Repo popularity

The repository has 0 stars and 0 forks, with only 2 watchers; this is weak supporting evidence of community adoption, though popularity alone is not decisive.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected; the build setup is credible while security-process transparency is limited.