bread/patterns

Its tiny dependency surface and stable release reduce integration uncertainty. The empty README and lack of security policy leave little guidance for a library, while organization backing does not show active maintenance.

Latest v1.1.0

Packagist

38%

Total Score

Maintainer Stability

100

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact includes a README entry, but it contains no text and the project has no tests or changelog. Missing tests and changelog are normal for published artifacts, while the empty consumer documentation is a real usability gap for a library.

Release history

The latest release was published in September 2013, with no releases in the last 12 months, indicating a long-standing abandonment risk. No newer release evidence compensates for this gap.

Repo popularity

The repository has zero stars, forks, and watchers, offering no evidence of community adoption. Popularity is supporting evidence only, so this reinforces rather than drives the maintenance concern.

Repo tooling

Composer is used for builds, but no security scanning tools are present. The missing scanning is a modest transparency gap, not evidence that the release is unsafe.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations unclear. This is a maintenance and transparency gap, though it is less significant for this very small, old package than its inactivity.