simenbkr/groupmanage

The narrow dependency surface and GPL license make the package straightforward to evaluate. Its documentation and project safeguards are thin, so adoption should be limited to code you can maintain yourself.

Latest 1.06

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published over six years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the package having seven releases overall.

Repo commit activity

The repository recorded no commits and no active maintainers in the measured three-month period, consistent with the long release gap and materially lowering confidence in ongoing maintenance.

Package scaffolding

The package has no README, tests, or changelog, although the GitHub release for this version is a useful documentation positive. The missing consumer documentation and tests remain meaningful gaps for a library.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is not required for a healthy package, but these figures provide no supporting evidence of community review or adoption.

Repo tooling

Composer is used for builds, but no security scanning tool is present. The small dependency surface partly limits exposure, yet the project has no automated security-checking evidence.