The README, matching repository, and GitHub release provide useful consumer and publication context. Maintenance evidence is thin after the initial release, and the repository has no security policy.
60%
Total Score
50
100
83
83
One registry maintainer is consistent with a small user-owned project, but it leaves little visible publishing redundancy.
The registry namespace and repository are owned by the same individual account, showing consistent ownership but no organizational backing or maintainer redundancy.
The package has only one release, published about 11 months ago, so there is little release history to establish maturity or ongoing maintenance.
There were no commits and no active maintainers in the last three months, weakening evidence that defects or compatibility changes will be addressed promptly.
There were no new or closed issues or pull requests in the last month, and open issue count is unknown; this offers little evidence of active community support.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.0 | — | — |
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.