bluink/ratchet

Release historydanger

Only one release exists, published nearly two years ago, with no releases in the last 12 months. This is substantial evidence of limited ongoing maintenance.

Repo commit activitydanger

The repository had zero commits and zero active maintainers in the last three months, reinforcing the release-history concern and lowering confidence in current maintenance.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, and no pull requests were merged; this supports the picture of an inactive project, although the open-issues count is unknown.

Repo toolingcaution

The project uses Composer and Make, but no security-scanning tools were detected. That is a modest transparency and maintenance gap, not a severe risk by itself.

Workflow auditcaution

The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all three action references are unpinned, which leaves avoidable build-integrity risk.