The package has no automated tests or security scanning, leaving maintenance quality difficult to verify. MIT licensing, a matching repository, and release notes for version 1.0.1 provide useful transparency, but do not offset the long inactivity.
42%
Total Score
0
75
75
Only two releases were published, with the latest over five years ago and none in the last 12 months. This is strong evidence of abandonment risk for a maintained SDK.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing prolonged inactivity.
The repository has zero stars and only one fork or watcher. Popularity is supporting evidence rather than a verdict, but these counters provide little evidence of a broad maintainer or user community.
Composer is used for builds, but no security scanning tools are configured. That weakens ongoing maintenance and vulnerability-detection transparency.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a meaningful transparency gap for an SDK handling email-related API integration.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version 6.5.* | — | — |
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.