The repository is small and new, with most recent work from one contributor. Clear licensing, repository tests, active commits, organization backing, and read-only workflow permissions reduce adoption risk, but CI references are all unpinned and no security policy or scanning is present.
68%
Total Score
83
81
75
The package is only 43 days old and has five releases, with a median interval of about 14 hours. This shows active early development but provides limited evidence of long-term maintenance.
Two contributors are active, but one accounts for 90% of the last three months' commits. That concentration leaves meaningful continuity risk despite the second contributor's presence.
Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and maintenance gap rather than evidence of unsafe code.
The repository has no security policy. For a platform-specific library this reduces reporting transparency, though it is not by itself evidence of abandonment.
Version 0.7.6 is not a prerelease, and recent releases contain no prereleases, which supports predictable adoption. It remains below a stable major version, so compatibility maturity is still limited.
We didn't find any vulnerabilities for this package.
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.