pekhota/nova-multifile

The package is documented, licensed, tested in its repository, and has a focused dependency footprint. Its small, single-maintainer project has not committed in the last three months, while all four workflow actions are unpinned. Pin this version only if the feature is needed and you can tolerate limited ongoing maintenance.

Latest v1.0.3

Packagist

60%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry publisher account is responsible for releases. The linked repository is also owned by the same individual, so this is not a registry-only mismatch, but it still indicates a thin maintainer base.

Project backing

The registry namespace and repository are owned by the same individual, with no organization backing indicated. This is consistent ownership but provides limited evidence of broader maintenance capacity.

Release history

The package is young at about four and a half months, with four releases clustered over roughly six days and no later release shown. That limited history makes long-term maintenance harder to establish.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. With the latest release about four months old, this is evidence of stalled maintenance rather than merely a brief pause.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. For a small package this is a hygiene gap, not evidence that the release is unsafe by itself.