The project includes tests, release notes, and security scanning. Its small audience and missing security policy reduce transparency; pin this version when adopting it.
72%
Total Score
50
100
100
75
The repository is owned by the same individual namespace as the package, confirming source alignment but offering no organizational backing to offset the concentrated maintainer base.
One contributor made 100% of the last three months' commits. The matching individual repository owner provides no organization-level handoff evidence, leaving a real continuity risk.
Six commits were made in the last three months, but all activity came from one maintainer, so maintenance is active but concentrated.
No repository security policy was found, reducing transparency about how users should report vulnerabilities in a package that handles application URLs and database-backed behavior.
All eight workflows were analyzed, but all 17 action references are unpinned; the audit also found high-confidence bot-condition and unpinned-container-image issues. The pull_request_target workflow had no untrusted checkout or script-injection sink, so these remain workflow hygiene concerns rather than standalone severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^11.0|^12.0|^13.0 | — | — |
spatie/laravel-model-info Version ^2.0 | — | — |
spatie/laravel-translatable Version ^6.0 | — | — |
spatie/laravel-package-tools Version ^1.9.2 | — | — |
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.