pspychalski/debug

Release historydanger

Only two releases exist, with the latest published in July 2015 and none in the last 11 years. This strongly raises abandonment risk despite the package reaching a stable 1.0.1 version.

Maintainerscaution

One registry account has publish access, leaving little visible publishing redundancy. The repository is user-owned rather than organization-backed, so the narrow maintainer base provides limited continuity assurance.

Repo commit activitycaution

The repository recorded no commits and no active maintainers in the last three months, consistent with the long gap since its last release. This is a substantial maintenance concern, though not evidence that the package is malicious.

Repo toolingcaution

The project uses Composer but has no security scanning tools. The build tooling is appropriate, while the missing scanning reduces transparency around ongoing maintenance.

Security policycaution

The linked repository has no security policy. For a small, inactive package this adds a transparency gap and gives users no documented route for reporting vulnerabilities.