absuite/suite-cbo

The stable major version, matching source repository, and lack of install scripts provide useful safeguards. A single registry maintainer, no security policy, and an effectively empty README leave limited transparency for ongoing use.

Latest 1.2.30

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was over eight years ago, with no releases in the last 12 months. Fourteen releases show an earlier development history, but the prolonged gap is a substantial abandonment concern.

Maintainers

Only one registry account has publish access. Because the repository is user-owned rather than organization-owned, this provides limited evidence of publishing continuity and leaves a thin apparent maintainer base.

Package scaffolding

The package includes a README file and has a GitHub release for this version, but the README contains zero characters and the source repository has no tests or changelog. The absent tests and changelog are normal packaging practice, while the empty README limits consumer transparency.

Repo tooling

Composer is used as the build tool, but no security scanning tools are present. The build setup is clear, while the missing security tooling is a modest transparency and maintenance gap.

Repository archived

The repository is not archived, which is a compensating sign, but it was last pushed over seven years ago. That stale source activity materially increases maintenance risk.