middlewares/debugbar

Clear documentation, repository tests, and a stable release line make integration straightforward. Maintenance has been quiet for about 18 months, and the workflow uses all five actions without pinning; no security policy is present.

Latest v2.2.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has existed since 2016 with 16 releases, but it had no releases in the last 12 months despite the latest release being about 18 months old. This indicates materially slowed maintenance, though the long history provides some maturity evidence.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the absence of recent releases. This is a real maintenance concern, even though the repository is not archived.

Repo issue activity

There are no open issues or pull requests, and no recent issue or pull request activity. This is compatible with a quiet, stable project but does not demonstrate active maintenance.

Repo tooling

The repository uses Composer build tooling, but no security scanning tools were detected. The missing scanning is a modest transparency and hygiene gap, not evidence of unsafe behavior by itself.

Security policy

No security policy was found in the repository. For a library that processes HTTP responses, this leaves vulnerability reporting and response expectations undocumented.