The README, release notes, license, and organization ownership provide useful documentation and basic project structure. Security maintenance is less transparent because no security policy or scanning is present.
58%
Total Score
75
83
75
The latest release was over two years ago and there were no releases in the last 12 months, which is a meaningful maintenance concern for a dependency. The six-release history shows the package was previously published but does not offset the current inactivity.
The repository had no commits and no active maintainers in the last three months, consistent with the long release gap and raising abandonment risk. The repository is not archived, but that does not demonstrate ongoing maintenance.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap rather than evidence that the package is unsafe.
The current v0.2.6 release is not marked prerelease, but the package remains below major version 1 and has a mixed recent prerelease history, indicating a relatively immature API.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/pulse Version ^1.0.0@beta | — | — |
illuminate/support Version * | — | — |
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.