arsku/composer-example-package

Release historydanger

The package has 4 releases, all clustered on 1 May 2017, with 0 releases in the last 12 months and nearly nine years since the latest release. This is strong evidence of abandonment for a dependency.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last three months. Combined with the old release history, this indicates that maintenance has effectively stopped.

Project backingcaution

The registry namespace and repository are owned by individual accounts rather than an organization. This is not inherently unhealthy, but it provides no organizational backing to compensate for the thin maintenance history.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month. With the repository already inactive for years, this supports the conclusion that there is little ongoing project activity.

Repo package mentioncaution

The repository name does not match the package name, and no README mention was available. A mismatch can be normal for subpackages, but here the absence of a confirming mention creates uncertainty that the repository belongs to this package.