Security documentation is absent, and the project has little visible community support. Its README, MIT license, and minimal runtime dependencies make integration straightforward, but ongoing maintenance remains uncertain.
58%
Total Score
50
100
83
83
There were no commits and no active maintainers in the last three months, consistent with the absence of releases over the last year. This is a meaningful abandonment risk for a young SDK.
The package has only two releases, both in August 2025, and none in the last 12 months. This limited and now-stalled release history raises maintenance concerns.
The repository has only 2 stars, 0 forks, and 1 watcher, indicating limited visible adoption or community support. Popularity is supporting evidence, so this modestly lowers confidence rather than deciding the result alone.
Composer is used for the build, but no security-scanning tool is configured. The missing scanning is a hygiene weakness, though it is less significant than the maintenance gap.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap for an SDK that handles email service credentials and data.
We didn't find any vulnerabilities for this package.
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.