A clear README, release notes, repository tests, and a security policy improve confidence for adopters. The workflow uses four unpinned actions and installs a package outside a lockfile, while all recent commits come from one contributor; pinning the workflow and adding another active maintainer would reduce risk.
82%
Total Score
75
100
75
All 15 recent commits came from one contributor, so maintenance depends heavily on a single person and has limited handoff resilience.
The only workflow was fully analyzed and has no untrusted checkout or script-injection path, but all four action references are unpinned and the high-confidence audit found an ad hoc package installation outside a lockfile.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
filament/filament Version ^5.0 | — | — |
carlos-meneses/laravel-mpdf Version ^2.1.11 | — | — |
mortezamasumi/fb-essentials Version ^5.0 | — | — |
spatie/laravel-package-tools Version ^1.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.