3lvir4/funfp

The MIT license, tests, README, matching repository, and no runtime dependencies support straightforward adoption. The project has limited outside activity and workflow pinning, so future maintenance and build integrity deserve attention.

Latest v0.0.3

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access, which is a thin publishing base for a user-owned project. This is consistent with the matching single-owner repository but still leaves limited redundancy.

Release history

The latest release was about 2 years and 5 months ago, with no releases in the last 12 months. Its three releases were initially spaced about 16 days apart, but that activity has stopped.

Repo commit activity

There were no commits and no active maintainers in the last 3 months, consistent with the long release gap and indicating that maintenance has effectively stopped.

Repo popularity

The repository has zero stars and forks and one watcher, providing little evidence of external adoption or review. Popularity is supporting evidence, so this lowers confidence in maturity without deciding the verdict alone.

Repo tooling

Composer is used as the build tool, but no security scanning tool was detected. The missing scanner is a hygiene gap rather than evidence that the package is unsafe.