musoftware/logger-php

Release historydanger

The package has 107 releases since 2012, but its latest release was on February 3, 2024, with no releases in the following roughly two years and seven months. That long gap raises abandonment risk despite its historically regular cadence.

Repo package mentiondanger

The repository name matches the package, but its README does not mention musoftware/logger-php and instead presents the Sentry PHP SDK. That mismatch makes package ownership and source provenance unclear, which is a material adoption concern.

Project backingcaution

The registry namespace and repository owner both identify as musoftware, but the owner is an individual account rather than an organization. This offers limited backing evidence and does not compensate for the maintenance gap.

Security policycaution

No SECURITY.md or equivalent security policy was found, leaving vulnerability reporting and response expectations unclear. Repository scanning tooling partly compensates but does not replace a policy.

Workflow auditcaution

All 12 analyzed action references are unpinned, which weakens build reproducibility, and the audit reports a low-confidence cache-poisoning pattern. All three workflows use read-only permissions and have no untrusted checkouts or script injection, so the workflow concerns remain hygiene-level rather than severe.