Clear documentation, licensing, release notes, and organization backing support adoption. The small project has no recorded commits in the past three months and lacks a security policy or security-scanning tooling, so maintenance assurance remains limited.
62%
Total Score
75
100
86
75
The package has 3 releases over about 8 months, with a median interval of about 30 days; this shows an established release pattern, although the latest release was about 6 months ago.
The repository recorded 0 commits and 0 active maintainers in the past three months, which is a meaningful maintenance concern for a package released only recently.
Composer is used for the build, but no security-scanning tooling is present. This is a modest transparency and maintenance gap rather than evidence that the release is unsafe.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This weakens project transparency but is not severe enough to make the release unfit on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.0|^7.9|^7.10 | — | — |
sharpapi/php-core Version ^1.4.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.