srokap/code_review

The package includes tests, a README, and a clear MIT license. Its small dependency set and matching source repository improve transparency, but the project shows no active maintenance and lacks security-policy coverage.

Latest 1.0.6

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in May 2016, with no releases in the last 12 months and only three releases overall. This long release gap is strong evidence of abandonment for a package intended as an integration dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push occurring in May 2016. No newer maintenance activity compensates for this gap.

Project backing

The repository is owned by an individual user rather than an organization, and the registry has one maintainer. This is compatible with a small project, but it provides limited visible maintenance capacity when activity is absent.

Repo issue activity

There were no new or closed issues or pull requests in the last month, while six issues remain open. This suggests unresolved maintenance needs and little current project activity.

Repo tooling

Composer is used as a build tool, but no security-scanning tools are present. The missing scanning is a hygiene gap, especially alongside the project's long inactivity.