The package includes a clear README, a matching repository, and frequent recent releases. Its proprietary license permits use under its terms, while the project has no security policy or automated security scanning.
72%
Total Score
50
100
94
75
Only one registry account has publish access. That is a maintenance-continuity concern, although the linked repository shows current activity from the same owner.
The repository owner is an individual account rather than an organization, and the registry namespace matches that owner. This provides clear ownership but no organizational handoff capacity.
One contributor made all 15 commits in the last three months, giving the project a bus factor of one. The concentrated ownership increases abandonment and handoff risk.
The repository received 15 commits in the last three months, showing recent work. However, all activity came from one active maintainer, limiting independent continuity.
Composer is used for the build, but no security scanning tools were detected. This is a modest transparency and maintenance gap for a package that supplies executable PHP and frontend assets.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^12.0|^13.0 | — | — |
composer/installers Version ^2.0 | — | — |
appdezign/lara-pro-cms Version ^10.0 | — | — |
appdezign/lara-pro-base-theme Version ^10.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.