opxcms/opx-menu

The MIT license and matching repository make the package transparent to inspect. Its small dependency set and clean install path help, while the missing security policy leaves fewer signals about response readiness.

Latest 1.0.4

Packagist

45%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was over five years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite five total releases and a previously regular cadence.

Repo commit activity

There were no commits and no active maintainers in the measured three-month period. Combined with the last push being over five years ago, this materially raises abandonment risk.

Package scaffolding

The artifact includes a README, but it is only 10 characters long and offers little integration guidance. The absence of tests and a changelog in the published package is normal packaging practice, while the repository also provides neither.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. That is a moderate transparency and maintenance gap for a package with no recent activity.

Repository archived

The linked repository is not archived, so it remains technically available for inspection and possible maintenance. Its last push was over five years ago, however, which is consistent with the stale release history.