It has a small, tested codebase with a clear MIT license and no install-time scripts. The repository has no security policy or scanning, leaving maintenance and response capacity limited.
58%
Total Score
50
100
70
75
The package has had no releases in the last 12 months, and its latest release was about 18 months ago. Its five releases over roughly two years show some history, but the recent pause lowers confidence in ongoing maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release pause. This is a meaningful abandonment risk even though the repository is not archived.
The repository has 0 stars and 0 forks, with only 1 watcher. Popularity is not required for a healthy small package, but these numbers provide little supporting evidence of a maintained user base.
Composer build tooling is present, which supports reproducible project management, but no security scanning tools were detected. That leaves a gap in ongoing security hygiene.
The repository has no security policy, so consumers have no documented vulnerability-reporting or response process. This is a transparency gap for a package that handles closure serialization and related runtime behavior.
We didn't find any vulnerabilities for this package.
No maintainer information available.
No direct dependencies.
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.