Package Health/sidus/eav-permission-bundle

sidus/eav-permission-bundle

The documentation is clear and the package has a straightforward Composer dependency profile. Its last release was nearly seven years ago, with no recent issue activity, and the repository has no security policy. The single-user backing and repository/package mismatch add adoption risk.

Latest v2.0.2

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was in November 2019, nearly seven years ago, and there were no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.

Maintainers

Only one registry maintainer is listed, and the project backing signal identifies an individual owner. A single-person maintenance path increases continuity risk when release activity has already stopped.

Project backing

The repository is owned by an individual account rather than an organization. That is not inherently unhealthy, but it provides less visible continuity than organization backing for a package with no recent activity.

Repo issue activity

There were no new or closed issues or pull requests in the last month, while one issue remains open. Combined with the old release, this suggests little current maintenance activity.

Repo package mention

The repository name does not match the package name and its README does not mention the package. Although this could reflect packaging structure, the collected evidence does not clearly establish that the repository belongs to this release.