robertmain/communique

Release historydanger

The latest release was about 10 years ago, with no releases in the last 12 months and only four releases overall. This is strong evidence that the package is no longer actively maintained.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap. The repository was pushed more recently than the release, but not recently enough to show current maintenance.

Repo issue activitycaution

Seven issues and one pull request remain open, while there was no issue or pull-request activity in the last month. This suggests unresolved maintenance demand rather than an actively managed project.

Repo toolingcaution

Composer is used for the build, but no security-scanning tool was detected. This is a modest transparency and hygiene gap, not a severe dependency risk by itself.

Security policycaution

The repository has no security policy, so there is no documented route for reporting vulnerabilities or describing security handling. This matters for a REST client but does not outweigh the stronger maintenance concerns.