alwaysblank/brief

The package has a clear README, tests, a stable release, and only one runtime dependency. Its workflow uses read-only permissions, but its two actions are unpinned and no security policy is present.

Latest 3.0.1

Packagist

60%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry maintainer publishes the package, and the repository is owned by an individual rather than an organization. That is workable for a small package but leaves limited visible succession capacity when activity stops.

Release history

The latest release was published over three years ago, with no releases in the last 12 months. Earlier releases arrived regularly, so this indicates possible abandonment rather than an inherently immature project.

Repo commit activity

The repository has recorded no commits and no active maintainers in the last three months, consistent with the long release gap. This is the strongest maintenance concern in the available evidence.

Security policy

The repository has no security policy, reducing transparency about vulnerability reporting and maintenance handling. This is a modest concern rather than evidence that the release is unsafe.

Workflow audit

The workflow was fully analyzed, uses read-only permissions, and has no untrusted checkouts or script-injection findings. Both action references are unpinned, which is a minor supply-chain hygiene gap.