It includes a matching repository, tests, an Apache-2.0 license, and no install-time scripts. The project has no security scanning and no commit activity yet, so maintenance capacity is not established.
58%
Total Score
75
100
88
75
The package is newly published, with one release and no established release cadence. This is understandable for a first release but leaves maturity and maintenance history unproven.
The repository has zero commits and zero active maintainers in the last three months. Because the package is brand new, this may reflect its age, but there is not yet evidence of ongoing maintenance.
Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools were detected. That is a hygiene gap rather than evidence of an unsafe release.
The repository has no security policy. This weakens vulnerability-reporting transparency, although the small, newly created implementation repository provides limited history to assess.
No GitHub Actions workflows were present, so there are no workflow permissions, unpinned actions, or dangerous trigger findings. This also means no automated workflow-based validation or security checks were observed.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
laravel/serializable-closure Version 2.0.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.