Package Health/sectoroverload2k/php-crud

sectoroverload2k/php-crud

The tiny README gives consumers almost no integration guidance, and the repository has no recent commit activity or security scanning. Recent releases, a matching repository, and a simple dependency profile provide some support, but the project remains lightly maintained.

Latest 1.0.13

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A README is present, but it is only 10 characters long and provides little guidance for using this library. Missing tests and a changelog are expected packaging gaps and are not counted against it.

Project backing

The repository is owned by an individual user rather than an organization, so the single registry maintainer is consistent with the available project backing but leaves limited maintainer redundancy.

Repo commit activity

There were no commits and no active maintainers in the repository during the last three months. This is a meaningful maintenance concern despite the recent package release.

Repo popularity

The repository has no stars or forks and only one watcher. Low popularity is supporting evidence rather than a verdict, but it indicates limited visible community backing.

Repo tooling

Composer is used for the build, but no security scanning tool is configured. That weakens automated maintenance hygiene, although it is not evidence of malicious behavior by itself.