leafs/schema

Healthy and suitable to use, with a concentrated maintenance base as the main caveat. It has recent stable releases, tests, release notes, an active unarchived repository, and no risky workflow patterns, but all recent commits come from one contributor and the repository lacks a security policy.

Latest v5.0.1

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

One contributor made all seven commits in the last three months, leaving no demonstrated handoff capacity. Organization backing reduces the severity, but the concentration remains a maintenance risk.

Repo popularity

The repository has zero stars and two forks. This indicates limited public adoption, but popularity is supporting evidence and does not outweigh the recent releases, tests, and organizational backing.

Repo tooling

The project uses Composer for builds, but no security-scanning tool was detected. Build tooling is present; the missing scanning is a modest transparency and maintenance gap.

Security policy

The repository has no security policy. For a package that manages database schemas and is intended for application use, the lack of documented vulnerability-reporting guidance is a genuine transparency gap.

Token permissions

Neither workflow declares top-level token permissions, though neither declares top-level write access and the workflows show no dangerous patterns. This is a minor hardening gap rather than a severe workflow risk.