Laravel mail transport for Plunk API with event tracking and email verification
64%
Total Score
caution
No commits in three months and only three releases make maintenance less certain despite solid packaging and documentation.
The repository is owned by a User account rather than an organization, so the single registry maintainer represents a genuinely narrow apparent ownership base. The matching repository and release notes provide some compensating transparency.
The package is 531 days old with 3 releases, only 1 release in the last 12 months, and a median release interval of about 169 days. This indicates a slow maintenance cadence, although the latest release is recent enough to show the project is not abandoned.
The repository recorded 0 commits and 0 active maintainers in the last 3 months. That inactivity is a meaningful maintenance concern for a package integrating with an external email API.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy. This reduces transparency around vulnerability reporting and response expectations, though it is a moderate documentation gap rather than a standalone adoption blocker.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/mail Version ^10.0|^11.0|^12.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.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.