Clear licensing, documentation, repository tests, and organization backing improve adoption confidence. No commits were recorded in the last three months, while every workflow action is unpinned and the project has no security policy. The latest release and recent repository push provide some counterweight.
65%
Total Score
75
100
88
50
The package runs a post-autoload-dump install-time script. Lifecycle scripts can add installation complexity and supply-chain exposure, so this is a modest caution, though only one script is declared.
The package has six releases over about 1 year and 11 months, but only one release in the last 12 months. This suggests a slower cadence, although the latest release is recent and documented.
The repository recorded zero commits and zero active maintainers in the last three months. The recent release push shows the project is not abandoned outright, but ongoing maintenance activity is currently thin.
Composer build tooling is present, but no security-scanning tools were detected. For a package handling URLs, analytics, and webhooks, this leaves a meaningful security-maintenance gap.
The repository has no security policy. That reduces transparency about how vulnerabilities are reported and handled, even though other documentation is extensive.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
jenssegers/agent Version ^2.6 | — | — |
illuminate/contracts Version ^10.0 | ^11.0 | ^12.0 | ^13.0 | — | — |
cleaniquecoders/traitify Version ^1.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
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.