phossa/phossa-logger

Release historydanger

The package has had no releases in the last 12 months, and version 1.0.7 was published in April 2016 despite the package being mature. This long release gap materially increases abandonment and compatibility risk.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with the old last push, this is strong evidence that maintenance has effectively stopped.

Project backingcaution

The registry namespace and repository owner match, and the repository is user-owned rather than organization-owned. This supports package identity, though it provides limited evidence of a broader maintenance team.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a transparency gap, though it is secondary to the much larger maintenance concern.

Repository archivedcaution

The repository is not marked archived, but its last push was in November 2019, so the non-archived status does not offset the evidence of stale maintenance.