Package Health/graefe/doctrine-extensions

graefe/doctrine-extensions

The repository matches the package and contains tests, a README, and a declared MIT license. Its single-maintainer setup, absent security policy, and negligible repository activity leave limited evidence of long-term support.

Latest v0.3.0

Packagist

58%

Total Score

Maintainer Stability

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 four releases overall. The repository was pushed recently, but the long gap in published versions is a meaningful maintenance concern for consumers.

Maintainers

Only one registry account has publishing access, which limits publishing continuity if that maintainer becomes unavailable. The linked repository is owned by the same individual, so there is no organizational backing shown to offset that concentration.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide little independent evidence of broad adoption or community support.

Repo tooling

Composer is used as the build tool, but no security-scanning tools were detected. The missing scanning is a hygiene gap, while the standard build tooling supports reproducible project setup.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This lowers transparency but is not severe enough to make the release unfit on its own.