shipu/installer

Its compact structure and clear package contents make the project relatively easy to inspect. Long-term inactivity, minimal adoption, and missing security processes leave substantial abandonment and maintenance risk.

Latest v1.1

Packagist

35%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only 3 releases, all concentrated in July 2016, with no releases in the last 12 months and no meaningful subsequent release activity. This is strong evidence of abandonment risk.

Repo commit activity

There were 0 commits and 0 active maintainers in the last 3 months, consistent with the repository's last push in 2016. The lack of recent source activity materially increases maintenance and abandonment risk.

Lifecycle scripts

The package declares a post-update-cmd lifecycle script. This adds install/update execution surface that should be understood before adoption, although the signal does not show malicious or otherwise dangerous behavior.

Project backing

The package and repository are owned by the same individual account, so there is no mismatch in ownership context. Individual ownership is not inherently unhealthy, but it provides less organizational continuity than demonstrated project backing.

Repo popularity

The repository has 1 star, 1 fork, and 1 watcher, indicating very limited visible adoption. Popularity is supporting evidence rather than decisive, but this provides little external confidence or community support.