yunadmin/yunstorage

Clear documentation, an MIT license, and a small runtime dependency set make integration straightforward. Maintenance evidence is limited to one recent release and one contributor, with no tests or security policy.

Latest 1.0.0

Packagist

63%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A substantial README and changelog support consumers and document the release, while the absence of packaged tests is normal for a published artifact. Repository tests are also absent, limiting validation evidence.

Release history

The package is only 29 days old and has one release, so there is not enough history to demonstrate sustained maintenance or compatibility over time.

Repo bus factor

All recent commits came from one contributor, giving the project a single-person bus factor and increasing continuity risk if that contributor becomes unavailable.

Repo commit activity

Only one commit was recorded in the last three months from one active maintainer. Because the project is new, this is limited evidence rather than proof of a collapse, but it leaves maintenance capacity unproven.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap for a library handling cloud-storage credentials.