Package Health/oaksoftwaredev/yii2-sanitizer

oaksoftwaredev/yii2-sanitizer

The package is small and clearly identified, with an MIT license, a README, and only one runtime dependency. Its single maintainer, absent commits for over three years, and lack of tests or security tooling make long-term support a liability.

Latest 1.0.3

Packagist

45%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases exist, and none were published in the last 12 months; the latest release was over three years ago. This is strong evidence of stalled maintenance for a dependency consumers may need to keep compatible.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with the latest push being over three years ago. This is the clearest evidence that maintenance has stopped.

Maintainers

Only one registry publishing account is listed. Because the repository is user-owned rather than organization-backed, this represents a thin visible maintainer base and increases continuity risk.

Project backing

The repository is owned by a user account rather than an organization, and the registry namespace matches that owner. This supports package identity but offers little evidence of institutional backing.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap and compounds the limited maintenance evidence without proving the package is unsafe.