The package is clearly documented, licensed, and backed by repository tests and a changelog. Maintenance is thin, with one contributor and one commit in the last three months, while workflow controls remain weak.
62%
Total Score
50
100
50
Only one registry account has publish access. Because the repository is user-owned rather than organization-owned, this indicates limited publishing redundancy, though it does not by itself show abandonment.
All one recent commit came from a single contributor, giving the project a complete short-term bus-factor concentration with no provided organizational backing to compensate.
The repository recorded only one commit in the last three months from one active maintainer. That is thin recent maintenance for a library consumers may rely on.
The repository has no security policy. This is a transparency and vulnerability-reporting gap, especially for a library that handles external API credentials and data.
All five workflows were analyzed, but all 12 action references are unpinned and three workflows grant top-level write permissions. A high-confidence bot-conditions finding affects the Dependabot auto-merge workflow; no untrusted checkout or script injection was detected.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spatie/laravel-data Version ^4.17 | — | — |
illuminate/contracts Version ^11.0||^12.0||^13.0 | — | — |
crispchat/php-crisp-api Version ^1.7 | — | — |
php-http/guzzle7-adapter Version ^1.1 | — | — |
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.