The small, single-maintainer project has no tests, changelog, or security policy, limiting confidence in future fixes. Its MIT license, clear README, and direct repository match provide basic transparency, but not enough to offset the maintenance concern.
40%
Total Score
33
100
81
75
The latest release was published in December 2016, with no releases in the following nine years and nine months. That long gap is strong evidence of abandonment risk despite the package having a stable release history earlier on.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the nearly decade-long release gap and providing no evidence of current maintenance capacity.
The registry lists one maintainer, and project backing identifies an individual-owned repository. This is not inherently unhealthy, but it leaves limited visible continuity if that maintainer stops responding.
Seven issues remain open, while there were no new or closed issues or pull requests in the last month. This suggests unresolved maintenance demand with no recent response.
Composer build tooling is present, but no security-scanning tools were detected. This is a modest hygiene gap that compounds the lack of recent maintenance evidence.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
sendgrid/sendgrid Version 2.2.1 | — | — |
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.