brick/reflection

A small, organization-backed project has a clear release trail, tests, and release notes. Its recent inactivity, absent security scanning, and unpinned CI actions leave meaningful maintenance and build-integrity gaps.

Latest 0.7.1

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository recorded no commits and no active maintainers in the last 3 months. That recent inactivity is a meaningful maintenance concern, although the release history shows the project has not been abandoned for years.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. This leaves a gap in the project's automated security hygiene.

Security policy

The repository has no security policy. For a small library this is not severe by itself, but it reduces transparency about vulnerability reporting and handling.

Version stability

Version 0.7.1 is not a prerelease, and no recent releases are prereleases. The pre-1.0 major version still signals some API-change risk, but it is not an abandonment concern.

Workflow audit

The single workflow was fully analyzed with no untrusted checkout or script-injection findings, but all 8 action references are unpinned. The lack of a top-level permissions block is acceptable on its own and is not the concern here.