Package Health/mayflower/php-codebrowser

mayflower/php-codebrowser

Usable with caveats: this is a mature, well-structured package with a clear repository, tests, releases, and a permissive license. However, it has had no registry releases or repository commits for about 2 years and 6 months, so future fixes and compatibility work are uncertain.

Latest 4.0.1

Packagist

65%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 19 releases over more than 12 years, but none in the last 12 months and the latest release was about 2 years and 6 months ago. This indicates materially slowed maintenance despite a historically established release record.

Repo commit activity

There were no commits and no active maintainers in the last 3 months, consistent with a repository that has been inactive since the latest release about 2 years and 6 months ago. This is the main maintenance and abandonment concern.

Repo issue activity

There are only 5 open issues and no recent issue or pull-request activity. The small backlog is not severe, but the lack of recent responses provides little evidence of active support.

Repo tooling

Composer, Phing, and Box are used for building, showing established project tooling. No security scanning tools were detected, which is a hygiene gap, but it is less decisive than the demonstrated build setup.

Security policy

The repository has no security policy. This reduces transparency about vulnerability reporting and maintenance expectations, although it is a secondary concern for the overall dependency decision.