simonecosci/wtf-game

The repository is intact and the package includes tests, a README, and matching source references. Its Composer lifecycle scripts and missing security policy add maintenance and release-hygiene concerns for an application that has seen no recent development.

Latest 0.0.3

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in about 7 years and 5 months, with zero releases in the last 12 months. This is strong evidence of abandonment for a dependency, despite having three releases overall.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the long release gap, this materially increases abandonment risk.

Lifecycle scripts

The package uses five Composer lifecycle scripts, including install and create-project hooks. These are common for a Laravel application but increase the amount of code executed during installation and warrant extra release scrutiny.

Project backing

The package and repository are owned by the same individual account rather than an organization. That is consistent ownership, but it provides limited maintainer capacity or continuity.

Repo issue activity

There are 19 open pull requests but no new or closed issues or merged pull requests in the last month, suggesting unresolved maintenance activity rather than an actively managed project.