kerigard/laravel-stubs

The repository is licensed, tested, and clearly matched to the package, while workflows completed without audit findings. One maintainer, no prior release history, and three unpinned workflow actions leave support and build reproducibility uncertain.

Latest v1.0.0

Packagist

67%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry publishing maintainer is listed. That is workable for a small package but leaves limited visible publishing redundancy.

Release history

This is the first release, published today, so there is no track record for maintenance or release consistency yet. Its immediate publication is not itself a severe concern.

Repo commit activity

There were no commits or active maintainers in the last three months, but the repository was only created or updated today, so this is mainly an absence of history rather than evidence of collapse.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a hygiene gap rather than evidence that the release is unsafe.

Security policy

The repository has no security policy, reducing transparency about how vulnerabilities should be reported. For a new, small package this is a moderate documentation gap.