joycezhang/laravellib

The MIT license, stable versioning, README, and release notes make integration clearer. The small user-owned project has no security policy or scanning, limiting visible safeguards and confidence in future maintenance.

Latest 2.4.8

Packagist

54%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry publisher account is listed, which indicates a thin publishing base. The linked user-owned repository provides some continuity, but it does not offset the limited visible capacity fully.

Release history

The package has 28 releases since 2020, but none in the last 12 months and the latest release was over two years ago. That established history is positive, but the prolonged release gap raises maintenance risk.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the long registry release gap. This is the strongest evidence of current maintenance risk.

Repo tooling

The repository uses Composer, but no security scanning tools were detected. Build tooling is present, while automated security coverage is not visible.

Security policy

The repository has no security policy, leaving the process for reporting and handling vulnerabilities unspecified.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

joycezhangw

Direct Dependencies

Dependency	Last Release	Score
illuminate/http Version ^8.0\|^9.0\|^10.0	—	—
illuminate/cache Version ^8.0\|^9.0\|^10.0	—	—
illuminate/config Version ^8.0\|^9.0\|^10.0	—	—
illuminate/console Version ^8.0\|^9.0\|^10.0	—	—
illuminate/support Version ^8.0\|^9.0\|^10.0	—	—