Clear documentation, tests, and licensing reduce adoption friction. The broad dependency footprint and unpinned CI actions add maintenance and update risk.
52%
Total Score
50
50
86
67
Thirty-eight runtime dependencies create a large transitive maintenance and compatibility surface for a v1.0.0 package. The declared integrations explain some breadth, but do not remove the upgrade burden.
A post-update Composer script runs during dependency updates. This is not inherently unsafe, but it adds installation behavior that consumers should understand before adoption.
This is the only release, published 474 days ago, with no releases in the last 12 months. That leaves little evidence of ongoing maintenance for a package with a broad feature and dependency scope.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the lack of releases over more than a year. This is a meaningful abandonment concern.
Composer build tooling is present, but no security scanning tools were detected. That is a transparency and maintenance gap, though the available tests and CI provide some compensating evidence.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
prism-php/prism Version ^1.0 | — | — |
guzzlehttp/guzzle Version ^7.0 | — | — |
spatie/schema-org Version ^3.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0 | — | — |
spatie/laravel-ray Version ^2.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.