wuliaowyh/alioss

The README, tests, MIT license, and focused dependency keep the package understandable. Its single-maintainer, one-star project lacks security scanning and has no recent activity, making future compatibility uncertain.

Latest 1.0.6

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in nearly 7 years: all 7 releases were published between June 6 and June 25, 2019, with none in the last 12 months. This is strong evidence of abandonment for a framework integration.

Maintainers

Only one registry publishing account is listed. That is a thin publishing base, and no organization backing is shown to compensate for the limited maintainer capacity.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the release history and leaving compatibility fixes unlikely.

Repo popularity

The repository has 1 star, 0 forks, and 0 watchers. Popularity is only supporting evidence, but this provides little community evidence to offset the long inactivity.

Repo tooling

Composer is used as the build tool, which fits the package, but no security scanning tool is configured. This is a modest transparency and maintenance gap rather than a standalone severe risk.