lesname/database

Recent releases, repository tests, and read-only workflow permissions support continued maintenance. A single active contributor, no package README, and unpinned actions leave adoption dependent on limited ownership and weaker build reproducibility.

Latest 0.5.7

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact has no README, which weakens consumer documentation for a library, but the repository contains tests and uses GitHub releases, partly compensating for the missing artifact documentation.

Repo bus factor

All 8 recent commits came from one contributor. Organization ownership provides some handoff capacity, but no second active contributor is shown, leaving a thin operational base.

Repo package mention

The repository name does not match the package name, and no README mention was found, so the linkage is less transparent and the package may be a subproject or poorly documented repository pairing.

Security policy

The repository has no published security policy, leaving vulnerability-reporting expectations unclear; this is a transparency gap but not evidence of abandonment.

Version stability

Version 0.5.7 is not a stable-major release, but it is not a prerelease and recent releases contain no prerelease versions, so the maturity concern is limited.