Polymorphic notes with attachments for Laravel applications
70%
Total Score
caution
Usable with caveats: a young project with all recent commits from one contributor.
The package runs a post-autoload-dump install-time lifecycle script. The signal does not show harmful behavior, but any install-time execution adds a small supply-chain review concern.
One contributor made all 4 commits in the last 3 months, creating a concentrated maintenance dependency. The organization-owned repository provides some handoff capacity, but no second active contributor is shown.
Composer build tooling is present, but no security scanning tool was detected. This is a transparency and maintenance gap rather than evidence of an unsafe release.
The repository has no security policy. For a Laravel library handling notes, users, and attachments, that weakens the documented process for reporting and handling vulnerabilities.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, or audit findings, but both referenced actions are unpinned. The missing top-level permissions block is acceptable on its own; unpinned actions remain a minor reproducibility and supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^11.0|^12.0|^13.0 | — | — |
illuminate/support Version ^11.0|^12.0|^13.0 | — | — |
illuminate/database Version ^11.0|^12.0|^13.0 | — | — |
spatie/laravel-data Version ^4.0 | — | — |
illuminate/contracts Version ^11.0|^12.0|^13.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.