Clear documentation, tests, and a changelog make the package straightforward to inspect. However, its tiny user base and absent security policy increase maintenance risk alongside the long period without releases or commits.
52%
Total Score
0
75
75
The package has had only two releases, with the latest published nearly nine years ago and none in the last 12 months. This is strong evidence of stagnation for a library tied to an external API.
The repository recorded zero commits and zero active maintainers in the last three months, while its last push was nearly eight years ago. The repository is not archived, but observed maintenance activity is effectively absent.
The repository has only 2 stars, 1 fork, and 2 watchers, providing little evidence of a broad user or contributor base to help sustain the package.
The project uses Composer, which supports reproducible package builds, but no security-scanning tooling was detected. The lack of scanning modestly reduces maintenance confidence.
The linked repository has no security policy, leaving vulnerability-reporting expectations and response procedures undocumented. This is a transparency and maintenance gap, though it is not a severe risk by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.2 | — | — |
cloudinary/cloudinary_php Version ^1.7 | — | — |
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.