Usable with caveats: the package is stable, licensed, tested, and clearly backed by an organization, but it has had no release or repository activity for about four years. The lack of a security policy and security scanning adds a smaller transparency concern.
58%
Total Score
75
100
88
88
The package has a long history and 15 releases, but its latest release was about four years ago and it had no releases in the last 12 months. That substantially raises abandonment and compatibility risk.
The repository recorded zero commits and zero active maintainers over the last three months, indicating that active development has effectively stopped.
There were no new or closed issues or pull requests in the last month, with six open issues and two open pull requests. This supports the conclusion that current maintenance is minimal.
Composer build tooling is present, but no security scanning tools were detected. For a dependency that handles mail transport, this is a modest transparency and maintenance gap.
The repository has no security policy, leaving users without a documented process for reporting vulnerabilities or understanding security maintenance expectations.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.0|^7.0 | — | — |
swiftmailer/swiftmailer Version ^6.0.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.