Package Health/ctw/ctw-composer-plugin-composerlenientplugin

ctw/ctw-composer-plugin-composerlenientplugin

Clear documentation and a small dependency surface make adoption easier. The main limitations are that one person made all 43 recent commits, no security scanning is reported, and the workflow uses one unpinned action.

Latest 2.0.3

Packagist

76%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by an individual rather than an organization, so there is no provided organizational backing to offset the concentrated maintainer base.

Repo bus factor

One contributor made 100% of the 43 commits in the last three months. Because the repository is user-owned rather than organization-owned, this concentration is a genuine continuity risk.

Repo tooling

Composer build tooling is present, but no security-scanning tool is reported. That is a modest transparency and maintenance gap, not evidence of unsafe behavior by itself.

Security policy

The repository has no security policy. For a Composer plugin that affects dependency resolution, this reduces the clarity of vulnerability reporting and response expectations.

Workflow audit

The workflow is fully analyzed, uses read-only permissions, and has no reported high- or medium-severity findings. Its single action reference is unpinned, leaving a minor reproducibility and action-integrity gap.