The project has tests, a clear license, and a repository that is still unarchived. Its small audience, missing security policy, and unpinned workflow actions add maintenance and build-transparency concerns.
45%
Total Score
50
100
78
75
The package has 20 releases, but none in the last 12 months; its latest release was in May 2021, roughly five years ago. This is strong evidence of abandonment risk for a runtime server component.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the roughly five-year release gap and materially increasing abandonment risk.
The repository has only 11 stars and 13 forks, indicating limited adoption and a smaller visible support community. Popularity is supporting evidence rather than decisive on its own, but it reinforces the maintenance concern.
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and hygiene gap rather than evidence of unsafe code.
The repository has no security policy, leaving vulnerability-reporting expectations and response procedures unclear.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
swoft/framework Version ~2.0.0 | — | — |
swoft/validator Version ~2.0.0 | — | — |
swoft/http-message Version ~2.0.0 | — | — |
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.