The package was published today and has no tests or repository security scanning, so its long-term reliability is not yet demonstrated. It is backed by an organization, has a clear README and MIT license, and is not deprecated or archived.
58%
Total Score
100
100
69
83
A substantial README and a GitHub release for this version support consumer transparency. The absence of tests and a changelog is not a packaging gap for this ecosystem, but the missing repository tests reduce evidence of project maturity.
The package is brand new, published today, with five releases concentrated within minutes; this shows active initial publication but provides no evidence of sustained maintenance.
The linked repository name does not match the package name and its README does not mention the package, making package-to-source ownership less transparent despite the matching organization owner.
The repository has zero stars, forks, and watchers. Because it was created or populated today, this is weak maturity evidence rather than a strong negative by itself.
Composer is used for builds, but no repository security scanning tools were detected. That is a modest transparency and maintenance gap for a package handling external service integration.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers Version ~1.0 || ~2.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.