umpirsky/extraload

Release historydanger

The package has only one release, published in April 2016, with no releases in the last 12 months. This is strong evidence that the published package is no longer actively maintained.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. The repository is not archived, but current maintenance capacity is effectively absent.

Project backingcaution

The registry namespace and repository owner match, providing consistent ownership context. The owner is an individual rather than an organization, so the single maintainer account offers limited visible backing.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, while five issues and one pull request remain open. This supports the concern that maintenance has stalled.

Repo toolingcaution

The repository uses Composer build tooling, but no security scanning tools were detected. This is a modest transparency and hygiene gap, not evidence of malicious behavior.