Regular releases and recent merged work support continued maintenance. The project has no security scanning, and all five workflow actions are unpinned, leaving avoidable upkeep and build-integrity gaps.
72%
Total Score
75
100
94
75
The package and repository are owned by the same individual account, so there is no organization backing shown to compensate for concentrated maintenance.
All 14 recent commits came from one contributor, giving the project a high handoff and continuity risk despite the recent activity.
Composer build tooling is present, but no security scanning tools were detected, leaving a transparency and maintenance-control gap.
The repository has no security policy, so there is no documented path for reporting vulnerabilities or explaining security handling.
Both workflows were fully analyzed with no dangerous triggers or audit findings, but all five action references are unpinned, which weakens build reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
statamic/cms Version ^6.10 | — | — |
laravel/prompts Version ^0.3.15 | — | — |
whitecube/lingua Version ^1.1 | — | — |
laravel/framework Version ^12.0 || ^13.0 | — | — |
spatie/schema-org Version ^3.23 | — | — |
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.