Recent releases and repository tests provide useful maintenance evidence, while the last three months show no commits or active maintainers. The workflow uses one unpinned action and the repository has no security policy, leaving moderate maintenance and build-transparency concerns.
68%
Total Score
67
50
94
67
Five runtime dependencies, including Laravel, Telescope, a Guzzle watcher, and helpers, create a meaningful dependency chain for a framework extension. The profile is not excessive, but compatibility depends on several upstream packages.
The repository recorded zero commits and zero active maintainers in the last three months. This is the strongest maintenance concern, although the recent release history and later repository push provide some compensating evidence.
There are two open issues and two open pull requests, but no new or closed issues or merged pull requests in the last month. This suggests limited current issue-handling activity.
Composer build tooling is present, but no security scanning tools were detected. For a small PHP extension this is a hygiene gap rather than evidence of abandonment.
The repository has no security policy. That weakens vulnerability-reporting transparency, though it is not by itself evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version >=12.0 | — | — |
laravel/telescope Version >=5.19 | — | — |
ronasit/laravel-helpers Version ^3.5.5 | — | — |
muhammadhuzaifa/telescope-guzzle-watcher Version >=4.1 | — | — |
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.