polakosz/mafab

The small release history and zero commits in the last three months limit confidence in ongoing maintenance. Tests, a matching README, a recent release, and a clean license partly offset concerns about one maintainer, no security policy, and unpinned workflow actions.

Latest v2.0.2

Packagist

65%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry publishing maintainer is listed, leaving a thin publishing base. This is a modest continuity concern for a small user-owned project, though repository activity shows the project is not abandoned outright.

Project backing

The package and repository are owned by the same individual account rather than an organization, so there is no visible organizational backing to offset the thin maintainer base.

Release history

The package is nearly eight years old but has only four releases, with a median interval of about two years and three months. One release in the last year and the recent latest release provide some evidence of continued ownership, but cadence is sparse.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. The recent repository push and release provide some compensation, but ongoing development activity is currently absent.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. For a small library this is a hygiene gap rather than evidence of abandonment.