Package Health/yakovenko/laravel-lighthouse-graphql-multi-schema

yakovenko/laravel-lighthouse-graphql-multi-schema

Security coverage is limited, and the project currently has no active contributors beyond its single maintainer. Frequent releases and a recent repository push provide useful evidence of ongoing ownership, while tests and a clear license support adoption.

Latest v2.3.1

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publishing access. That is a meaningful continuity risk for a user-owned project because release capacity depends on one person.

Project backing

The repository is owned by an individual account rather than an organization, so the single registry maintainer is not offset by visible organizational backing.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months. This conflicts with the frequent release history and is a caution for current maintenance continuity.

Repo tooling

Composer is used as a build tool, but no security scanning tools are present. The missing scanning layer weakens supply-chain hygiene without proving the package is unsafe.

Security policy

The repository has no security policy. That reduces transparency about vulnerability reporting and response expectations.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Alexander Yakovenko

Direct Dependencies

Dependency	Last Release	Score
laravel/framework Version ^9.0 \|\| ^10.0 \|\| ^11.0 \|\| ^12.0 \|\| ^13.0	—	—
nuwave/lighthouse Version ^6.0	—	—
haydenpierce/class-finder Version ^0.4 \|\| ^0.5	—	—