gabe/dayu

The package has only a brief README, no repository security policy, and no security-scanning tooling. It is not deprecated or archived, but its last release and commit were about 10 years ago, making maintenance risk too high for a new dependency.

Latest 0.1.2

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published about 10 years ago, with no releases in the last 12 months. Eleven releases show some historical activity, but there is no evidence of current maintenance.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the package's long period without a release.

Repo tooling

Composer build tooling is present, but no security-scanning tools are configured. That is a modest transparency and maintenance gap rather than a standalone severe risk.

Security policy

The repository has no security policy, leaving users without a documented reporting or response process. This matters more because the project has no recent maintenance evidence.

Version stability

Version 0.1.2 is not a stable-major release, which adds maturity risk for a package that has also seen no recent development.