swoft-fork/server

Release historydanger

There has been only one release, published over a year ago, with no releases in the last 12 months. That provides strong evidence of limited ongoing maintenance.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the release-history evidence of possible abandonment.

Repo toolingcaution

The project uses Composer build tooling, but no security-scanning tools were detected. This is a modest hygiene gap rather than evidence that the package is unsafe.

Security policycaution

The repository has no security policy. This is a transparency and response-process gap, though it is less serious than the evidence of inactive maintenance.

Workflow auditcaution

Both workflows were analyzed without high-confidence findings or unsafe trigger sinks, but all five action references are unpinned, leaving avoidable build-integrity exposure.