swoft/event
Clear licensing, tests, and a small dependency surface reduce adoption friction. However, its maintenance and workflow hygiene are weak, with no recent development and every analyzed action reference unpinned.
45%
Total Score
0
100
79
50
Health Score Breakdown
The latest release was about five years ago, and there were no releases in the last 12 months. Its earlier cadence was regular, but the long current gap signals abandonment risk.
The repository recorded zero commits and zero active maintainers over the last three months, consistent with the prolonged release gap. No provided activity signal compensates for this inactivity.
Composer build tooling is present, but no security-scanning tool was detected. That leaves maintenance and vulnerability-detection practices less transparent.
The repository has no security policy, which weakens vulnerability-reporting transparency. This is a hygiene concern rather than evidence that the package is unsafe by itself.
Both workflows were analyzed completely and had no dangerous triggers, untrusted checkouts, or audit findings. However, all 5 of 5 action references were unpinned, leaving avoidable build-integrity and reproducibility risk.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 swoft/stdlib Version ~2.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 5 years ago
- Created
- 7 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.