zero-to-prod/db-model

This is a transparent, actively published but very young package with a matching source repository, a clear MIT license, a substantial README, repository tests, reproducible-looking Composer-based structure, and no deprecation or dangerous workflow findings. The main adoption risks are limited maturity: the package is only 14 days old, has three releases, and repository activity consists of one commit from a single contributor in the last three months; the repository also lacks a security policy and automated security scanning. It may be reasonable for projects able to tolerate an immature dependency, but it should not yet be treated as a mature, low-maintenance foundation without monitoring.

Latest v0.2.1

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. That is a limited publishing base and adds continuity risk, with no provided organization backing to compensate for it.

Project backing

The repository is owned by the user account zero-to-prod rather than an organization, so the available evidence shows no organizational handoff or backing to offset the concentrated maintainer base.

Release history

The package is only 14 days old with three releases and a median release interval of about 7 days, so it has some release activity but very little history from which to judge long-term maintenance.

Repo bus factor

One contributor made 100% of the last three months' commits, creating a clear single-maintainer continuity risk; the repository owner is a user rather than an organization, so no project-backing compensation is shown.

Repo commit activity

There was one commit in the last three months from one active maintainer. The recent push is positive, but the very low activity provides limited evidence of sustained maintenance.