princebamm/flba

The single-maintainer project has no security scanning and its repository README does not mention the package. The MIT declaration and included tests, changelog, and README provide some transparency, but the project appears lightly maintained.

Latest 1.0.0

Packagist

49%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is 529 days old but has only two releases, both effectively published within the same day, with no releases in the last 12 months. This suggests a one-off or abandoned release line.

Maintainers

Only one registry account has publish access, leaving little visible publishing redundancy. The repository is user-owned, so there is no shown organizational backing to offset that thin maintainer base.

Repo commit activity

The repository had 0 commits and 0 active maintainers in the last three months, despite the package being assessed as a current dependency. This is meaningful abandonment risk.

Repo package mention

The repository name matches the package, but its README does not mention the package. That weakens confidence that the repository documents and supports the published dependency.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. That is a maintenance and transparency gap, though it is not severe by itself.