The package includes tests, a README, and a matching Apache-2.0 license, but its source has had no commits for about 21 months. Its README also warns that active maintenance is not guaranteed, while workflow action pinning and security-policy coverage are weak.
42%
Total Score
25
100
75
50
This is the only release, published about 21 months ago, with no releases in the last 12 months. The lack of a release cadence materially increases abandonment and compatibility risk.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old last push and single registry release, this is strong evidence of stalled maintenance.
The repository is owned by an individual account rather than an organization, so there is no demonstrated organizational backing to offset the thin maintenance record.
Composer build tooling is present, but no security-scanning tools were detected. That is a transparency and hygiene gap, though it is less severe than the clear maintenance inactivity.
The linked repository is not archived, which leaves a path for future maintenance. Its last push was about 21 months ago, so the non-archived status does not compensate for the observed inactivity.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
psr/container Version ^1.0 | — | — |
swoft-fork/event Version ~2.1.0 | — | — |
swoft-fork/stdlib Version ~2.1.0 | — | — |
swoft-fork/annotation Version ~2.1.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.