denisok94/admin

The package has a clear license, a matching repository, and no install-time scripts. Its long period without a release, limited adoption, and absent security policy increase maintenance risk.

Latest 0.1.7

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry publishing maintainer is consistent with an individually owned project, but it provides little redundancy if that maintainer becomes inactive. The long release gap makes this weakness more relevant.

Project backing

The package and repository are owned by the same individual account, providing consistent ownership context. There is no organization backing shown to compensate for the single-maintainer model.

Release history

The latest release was in June 2022, with no releases in the past four years despite nine releases overall. This is a meaningful maintenance concern, although the repository remains available and is not archived.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. This is consistent with a quiet project, but it does not demonstrate active maintenance.

Repo package mention

The repository name matches the package name, but the README does not mention the package. The name match reduces concern about a wrong repository, while the missing explicit mention leaves a small transparency gap.