tacoberu/bnf

The repository includes a full test suite, clear licensing, and readme documentation, with only one runtime dependency. Maintenance has gone quiet since the March 2025 release, and all four workflow actions are unpinned; the missing security scanning is an additional hygiene concern.

Latest v1.2.1

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry account has publish access. Because the repository is owned by an individual rather than an organization, this represents a relatively thin publishing base, although actual project activity is more relevant than access records alone.

Release history

The package has eight releases over roughly six years, but none in the last 12 months; the latest release was published in March 2025. This indicates a meaningful maintenance slowdown for a library dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. This is strong evidence that maintenance is currently inactive, though the March 2025 release and intact test suite provide some compensating maturity evidence.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. The clean queue is positive, but combined with zero recent commits it also provides little evidence of ongoing maintenance.

Repo tooling

Composer is used for the build, but no security scanning tool is configured. The lack of scanning is a hygiene gap rather than evidence that the release is unsafe by itself.