Usable with caveats: the package is clearly licensed, backed by a matching organization repository, and has tests, releases, and a stable v2.0.0. However, it has had no registry release in over a year and no commits in the last three months, with no security policy and incomplete workflow permission declarations.
68%
Total Score
75
86
67
The package has only three releases and none in the last 12 months; its latest release was published in February 2025. This indicates slow maintenance for a dependency, though the repository was updated around the same time and the package may be intentionally small and stable.
There were no commits and no active maintainers in the last three months. For a small package this may reflect stability, but it leaves current maintenance responsiveness uncertain.
The repository uses Composer build tooling, but no security scanning tools were detected. The absence of scanning is a maintainability and transparency gap, though it is not by itself evidence that the package is unsafe.
The repository has no security policy, so users have no documented reporting process for vulnerabilities. This is a genuine transparency gap for a package handling mail transport credentials.
Two workflows omit top-level token permissions, and one workflow declares top-level write access. The workflows show no dangerous patterns, but tighter permission declarations would reduce maintenance and automation risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^11.0 | — | — |
mailchimp/transactional Version ^1.0.59 | — | — |
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.