The project has had no commits or active maintainers for about five months, and its 12 releases arrived within a few minutes. It has a matching, licensed repository and clear README, but no tests or security policy are visible.
62%
Total Score
50
100
75
83
The repository is owned by a user account rather than an organization, and the registry maintainer list contains one person. This indicates a thin visible backing structure for ongoing maintenance.
All 12 releases were published within about 6 minutes, and no later release activity is shown over the package's 154-day age; this suggests a rapid initial burst rather than an established cadence.
There were zero commits and zero active maintainers in the last three months, despite the package being 154 days old. That is meaningful evidence of stalled maintenance for a new integration package.
The repository has zero stars, forks, and watchers. This is weak supporting evidence rather than a verdict, but it provides no external adoption signal for a young package.
Composer build tooling is present, but no security scanning tool was detected. The missing scanning is a hygiene gap, not evidence that the release is unsafe by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
filament/filament Version ^4.0 || ^5.0 | — | — |
laravel/framework Version ^11.0 || ^12.0 || ^13.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.