jjgrainger/wp-crumbs

The MIT license, focused dependency set, and clear README with release notes make the package easy to inspect and integrate. Its small repository remains available, but maintenance has effectively stopped, so future compatibility and fixes are uncertain.

Latest v1.0.2

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published more than 11 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the historically regular early release interval.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months, reinforcing that the package is not currently maintained.

Project backing

The registry namespace and repository owner match, and the repository is owned by the same individual rather than an organization. This supports package identity but offers limited evidence of maintenance capacity.

Repo tooling

Composer is used for project builds, but no security scanning tools were detected. The missing scanning is a minor transparency gap, secondary to the much stronger maintenance concern.

Security policy

The repository has no security policy. For a small, inactive package this reduces clarity about vulnerability reporting and response expectations.