Laravel handling incoming communication
68%
Total Score
caution
Usable with caveats: maintenance has been quiet, with no commits from active maintainers in the last three months.
The package has existed for about 5 years and released once in the last 12 months, with a median interval of about 9 months. The long intervals indicate a slower maintenance cadence, although a release was published recently.
There were no commits and no active maintainers in the last three months. This is meaningful evidence of quiet ongoing development, despite the recent package release.
The repository uses Composer for builds, but no security scanning tools were detected. The missing scanning is a modest maintenance and transparency gap, not evidence that the package is unsafe.
No security policy was found in the repository. This reduces transparency for reporting and handling vulnerabilities, though it is not by itself evidence of a vulnerability.
Both workflows were analyzed successfully with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all 6 action references are unpinned, creating a reproducibility and update-integrity gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^10.0 | — | — |
zbateson/mail-mime-parser Version ^3.0.6 | — | — |
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.