Package Health/hazardteam/autoclearchunk

hazardteam/autoclearchunk

The project has a clear license, useful documentation, and an organization-owned repository with a recent push. Maintenance evidence is thin: only two releases, no releases in the last 12 months, and no recorded commits or active maintainers in the last three months; security tooling is also absent.

Latest 3.0.2

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only two releases over about two years, with no release in the last 12 months and a median interval of about 432 days. This is meaningful maintenance caution, although the repository was pushed recently.

Repo commit activity

There were zero commits and zero active maintainers recorded in the last three months. This is the strongest maintenance concern, though the recent repository push partially offsets the abandonment signal.

Repo issue activity

One open issue and one open pull request remain, with no issues or pull requests opened or merged in the last month. This is a modest sign of limited project activity rather than a severe problem.

Repo popularity

Seven stars and three forks indicate a small user and contributor footprint. Popularity is only supporting evidence, but the limited reach offers little independent confidence in long-term maintenance.

Repo tooling

Composer is used for builds, but no security scanning tools are configured. The missing scanning is a hygiene gap, not evidence that the release is unsafe.