beyondcode/expose

Healthy and suitable to use, with a narrow maintenance caveat. It has regular releases, a current stable version, active organizational backing, tests, release notes, and a matching repository, but recent repository activity is limited to one contributor and the workflow lacks explicit token permissions.

Latest 3.2.4

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

All one commit in the last three months came from a single contributor. Organizational ownership provides some handoff capacity, but the observed recent activity remains concentrated.

Repo commit activity

Only one commit was recorded in the last three months, indicating a sharp short-term slowdown despite the recent release history.

Repo issue activity

There was one merged pull request in the last month, but no new or closed issues and no new pull requests, showing limited recent community activity.

Repo tooling

The repository uses Composer and Box for builds, which supports repeatable packaging, but no automated security-scanning tool was detected.

Security policy

The README gives a security contact, but the repository has no formal security policy file. This is a transparency gap for vulnerability handling, not evidence of unsafe code.