crisu83/yii-filemanager

Tests, a clear BSD-3-Clause license, and one runtime dependency make the package easy to inspect and integrate. Its single-maintainer project lacks a security policy and shows little community activity, increasing maintenance risk.

Latest 1.9.1

Packagist

32%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published on February 11, 2014, and there have been no releases in the last 12 months. This long period without updates is strong evidence of abandonment risk.

Repo commit activity

The repository had zero commits and zero active maintainers in the last three months, consistent with the prolonged release gap and indicating inactive maintenance.

Maintainers

Only one registry account has publish access. This is a thin maintainer base for an independently owned project and increases continuity risk if that maintainer is inactive.

Repo issue activity

There were no new or closed issues or pull requests in the last month, while one pull request remains open. This shows little current project activity.

Repo tooling

Composer is used for builds, but no security scanning tools are configured. The missing scanning is a hygiene gap that adds some transparency risk to an already inactive project.