Documentation, tests, and licensing are in place, and the repository clearly matches the package. Workflow hygiene is weak: all 11 action references are unpinned, with two high-confidence findings. The single maintainer and dormant issue queue add little support for renewed maintenance.
42%
Total Score
33
80
75
The package has made no releases in the last 12 months, and its latest release was about three years ago. Forty-five historical releases show prior activity but do not compensate for the prolonged current gap.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating a substantial abandonment risk.
Only one registry account has publish access. The repository is owned by the same individual, so the small registry list is not misleading, but it still indicates a thin maintainer base and limited continuity.
There were no new or closed issues or pull requests in the last month, while four issues and three pull requests remain open. This suggests the project is not actively tending its backlog.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, though it is less significant than the lack of recent maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
embed/embed Version ^4.4 | — | — |
doctrine/dbal Version ^3.3 | — | — |
filament/filament Version ^2.0 | — | — |
league/commonmark Version ^2.3 | — | — |
livewire/livewire Version ^2.10 | — | — |
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.