jwp/php-client

Release historydanger

The package has only one release, published over six years ago, with no releases in the last 12 months. That is strong evidence of limited ongoing maintenance.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with the single release, this indicates that maintenance has effectively stopped.

Repo issue activitycaution

There has been no new or closed issue activity in the last month, and two pull requests remain open. This suggests limited responsiveness, though the small project size reduces the weight of the finding.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package. Even with an otherwise plausible repository link, that mismatch leaves uncertainty about package provenance.

Repo toolingcaution

The repository uses Composer and Make, but no security-scanning tool was detected. For a small client this is a hygiene gap, not the main adoption concern.