intothesource/powerlogger

Release historydanger

The package has had no release in about 9 years; its four releases ended in August 2016. That long release gap is a substantial abandonment and compatibility concern.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the last push being in January 2017. No newer activity compensates for this prolonged inactivity.

Repo popularitycaution

The repository has 0 stars and 1 fork, providing little community evidence or backup for a package that has not been maintained recently. Popularity is supporting evidence, so this reinforces rather than independently determines the result.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. This is a modest transparency and maintenance gap, especially for a package handling application error data.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This adds a transparency concern, though it is less serious than the inactivity signals.