The project is very young, with only two releases and no commits in the past three months. Clear documentation, tests, release notes, and an MIT license help, but all three workflow actions are unpinned and no security policy is provided.
64%
Total Score
75
100
78
75
The package is only 130 days old and has released twice, with both releases arriving within about two days; this shows activity but not a proven long-term cadence.
There were zero commits and zero active maintainers in the past three months, a meaningful maintenance concern for a package that is still establishing itself.
The repository has zero stars, forks, and watchers. For a package only about four months old, this is limited supporting evidence rather than a decisive health problem.
Composer build tooling is present, but no security scanning tool was detected, leaving a modest transparency and maintenance gap.
The repository has no security policy, so the process for reporting and handling vulnerabilities is not documented.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.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.