croogo/menus

The focused dependency surface, included tests, and matching repository make the package easy to understand. Its release and commit activity stopped more than six years ago, while security scanning and a security policy are absent; pin this version only if its compatibility is already proven.

Latest 4.0.6

Packagist

56%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in more than six years, with zero releases in the last 12 months. Its earlier release history shows established use, but the long gap raises abandonment and compatibility risk.

Repo commit activity

There were no commits and no active maintainers in the past three months, consistent with the release history showing a long-maintenance gap. This materially increases the risk that compatibility or security issues will remain unaddressed.

Repo tooling

Composer is used for the build, but no security scanning tools are reported. That leaves a meaningful maintenance and dependency-review gap, although it is not evidence of a defect by itself.

Security policy

The repository has no security policy, so users have no documented reporting path or stated handling process for vulnerabilities. This is a transparency gap, especially for a package with no recent maintenance activity.