nuka9510/ffp

This release is usable but too new to be considered mature: it has only one release published today, no tests or changelog in either the artifact or repository, no security policy, and no security scanning configuration. The repository is active enough to be unarchived and was pushed shortly before assessment, and the package has a clear matching repository, MIT licensing, minimal runtime dependencies, no install lifecycle scripts, and no deprecation status. Overall, the main risk is limited evidence of maintenance depth and release maturity rather than a specific indication that the package is unsafe to depend on.

Latest v1.1.1

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A substantial README is present, but neither the package artifact nor repository contains tests or a changelog. For a framework intended for application use, the absence of both reduces confidence in regression coverage and release transparency.

Project backing

The repository is owned by an individual user rather than an organization, so there is no visible organizational backing to compensate for the package's single-maintainer and new-project profile.

Release history

The package is brand new, with one release and no established release cadence. This materially limits evidence of maturity and maintenance reliability.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. With only one release, this is insufficient to demonstrate community support or maintenance responsiveness, but it is not itself evidence of abandonment.

Repo popularity

The repository has zero stars, forks, and watchers. For a package released today this is weak but unsurprising evidence, so it lowers maturity confidence without independently making the package unfit.