Send laravel notification using speeda mobile
61%
Total Score
50
100
94
83
One registry maintainer is consistent with the repository being owned by an individual, but it leaves little publishing redundancy if that maintainer becomes unavailable.
The repository is owned by an individual rather than an organization, so the single registry maintainer does not have organizational backing to compensate for a thin maintainer base.
The package has existed since February 2022 and has four releases, but only one release appeared in the last 12 months with a median interval of about 238 days. This indicates a slow release cadence rather than active ongoing delivery.
There were zero commits and zero active maintainers in the last three months. Combined with the slow release cadence, this is evidence of currently limited maintenance activity.
All four workflows were analyzed, but all nine action references are unpinned, and a high-confidence bot-conditions finding reports spoofable actor context in the Dependabot auto-merge workflow. The pull_request_target trigger has no untrusted checkout or script-injection sink, so this is a meaningful hygiene concern rather than a severe standalone risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^11|^v12 | — | — |
spatie/laravel-package-tools Version ^1.92.7 | — | — |
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.