Example of Openswoole
68%
Total Score
caution
Usable with caveats: quiet recent maintenance and an unpinned workflow action reduce confidence.
Only 1 release was published in the last 12 months, with a median interval of about 174 days across 5 releases. The latest release is recent, which partly offsets the slow cadence but still suggests limited ongoing change.
The repository recorded 0 commits and 0 active maintainers in the last 3 months. The recent package release and repository push provide some compensation, but current development activity remains thin.
Composer build tooling is present, but no security-scanning tools were detected. For an executable example project, that leaves a meaningful transparency and maintenance gap.
The repository has no security policy. This weakens the project's documented process for reporting and handling vulnerabilities.
All workflows were analyzed with no audit findings or untrusted execution paths, but the single action reference is unpinned. The missing top-level permissions block is acceptable on its own, while the unpinned dependency is a modest supply-chain hygiene concern.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
slim/psr7 Version dev-master | — | — |
slim/slim Version ^4.0 | — | — |
openswoole/core Version >=26.2 | — | — |
league/container Version 4.x-dev | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.