swoft-fork/websocket-server

Release historydanger

Only one release exists, published about 1 year 9 months ago, with no releases in the last 12 months. That leaves little evidence of ongoing maintenance for a production dependency.

Repo commit activitydanger

The repository had zero commits and zero active maintainers in the last 3 months, reinforcing the package's explicit maintenance warning and creating substantial abandonment risk.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest process gap, especially for a package intended to run as a server component.

Security policycaution

The repository has no security policy, reducing transparency for reporting and handling vulnerabilities in a network-facing WebSocket component.

Workflow auditcaution

Both workflows were analyzed successfully with no untrusted checkouts, script injection, or high-confidence audit findings. However, all 5 action references are unpinned, leaving avoidable build-integrity risk.