Recent release activity and organization backing support continued ownership. Three months without commits and no security policy reduce transparency, though tests, licensing, and release notes are in place.
68%
Total Score
75
100
94
83
There were no commits and no active maintainers in the last three months, which lowers confidence in ongoing maintenance. The repository's push today and release today partly compensate but do not erase the thin recent activity.
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and hygiene gap rather than evidence that the release is unsafe.
The repository has no published security policy, leaving vulnerability reporting and handling expectations unclear.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
neos/neos Version ^5.0 || ^7.0 || ^8.0 | — | — |
ankitpokhrel/tus-php Version ^2.1 | — | — |
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.