krazzer/wp-issue-logger

Release historydanger

Only two releases exist, with the latest published about four years ago and none in the last 12 months. That long gap materially raises abandonment risk for a dependency.

Repo commit activitydanger

There were no commits and no active maintainers during the last three months, consistent with the long release gap and indicating no current maintenance capacity.

Project backingcaution

The package and repository are consistently owned by the same individual account, so there is no ownership mismatch. However, individual ownership provides less organizational maintenance capacity than a backed project, especially alongside inactivity.

Repo popularitycaution

The repository has zero stars and forks and only one watcher, so there is little visible community support to offset the single-maintainer and inactivity concerns.

Repo toolingcaution

The repository uses Composer, which supports reproducible package management, but it has no security scanning tooling. For this small package that is a secondary transparency gap rather than a standalone severe risk.