staabm/whoops

Release historydanger

The latest registry release was about eight years ago, with no releases in the last 12 months. That substantially increases the risk that this published version is stale, despite the linked repository being updated more recently.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. Combined with no registry releases for about eight years, this points to slowed maintenance and raises abandonment risk.

Maintainerscaution

One registry account has publish access. This is a limited publishing base, but the repository is owned by the same individual, so it is consistent rather than unexplained.

Project backingcaution

The registry namespace and repository are owned by the same individual account, providing consistent ownership context but no organization backing or broader maintainer base.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool was detected. The missing scanner is a hygiene gap rather than proof of an unsafe release.