The package has clear documentation, release notes, tests in the source tree, and matching Apache-2.0 licensing. However, it has had no release for about 8 years, no recent commits, no security policy, and the repository does not identify or mention this package, making continued maintenance and provenance uncertain.
42%
Total Score
25
75
75
The latest release was about 8 years ago, with no releases in the past 12 months. This is strong evidence of abandonment risk for a library tied to an external service.
The repository recorded no commits and no active maintainers in the past 3 months, consistent with the long release silence and leaving little evidence of ongoing maintenance.
There were no newly opened or closed issues or pull requests in the past month, while 18 issues remain open. This adds to the evidence of limited current project activity.
The repository name does not match the package name and its README does not mention the package. Although this can occur with subpackages, the absence of either link weakens provenance confidence.
Composer build tooling is present, but no security scanning tools were detected. This is a modest hygiene gap and does not outweigh the stronger maintenance concerns.
We didn't find any vulnerabilities for this package.
No maintainer information available.
No direct dependencies.
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.