The README, repository tests, release notes, and MIT licensing provide useful transparency. Workflow references are unpinned, security scanning is absent, and the package has no established maintenance history yet.
58%
Total Score
50
88
67
Only one registry publishing account is listed, and the repository is owned by a single user rather than an organization. This is a thin observed maintainer base for a package with no established history.
This package is 0 days old with only 3 releases, all published within roughly 1 hour; that is too little history to establish dependable maintenance or release practices.
The repository shows 0 commits and 0 active maintainers over the last 3 months. Because the package is brand new, this may reflect limited observation time, but it still provides no demonstrated ongoing maintenance.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap, not evidence that the package is unsafe.
The repository has no security policy. For a package handling SMTP credentials and mailbox administration, this leaves vulnerability-reporting expectations undocumented.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/mime Version ^7.0|^8.0 | — | — |
symfony/mailer Version ^7.0|^8.0 | — | — |
guzzlehttp/guzzle Version ^7.5 | — | — |
illuminate/support Version ^12.0|^13.0 | — | — |
illuminate/contracts Version ^12.0|^13.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.