The project has had no commits in the last three months and no releases in over two years, with no visible security policy. It is not archived and includes tests, so the main concern is stale maintenance rather than immediate abandonment.
58%
Total Score
50
70
50
The latest release was over two years ago, and there were no releases in the last 12 months. That indicates materially stale maintenance for a library consumers may need to keep compatible.
The repository recorded zero commits and zero active maintainers in the last three months. This is direct evidence that current maintenance capacity is weak.
The repository name matches the package, which supports the link, but the README does not mention the package. That leaves a small transparency gap for consumers trying to verify the source.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these figures provide little evidence of a broader support community.
The repository has no security policy. This reduces transparency and gives users no documented route for reporting vulnerabilities, though it is not by itself evidence of unsafe code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version * | — | — |
laravel/framework Version * | — | — |
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.