Clear licensing, tests, documentation, and a long release history support adoption. The organization-backed repository lacks recent recorded commits and a security policy, while the repository-name mismatch reduces transparency.
70%
Total Score
75
88
83
No commits and no active maintainers were recorded in the last 3 months, despite a recent package release; this weakens evidence of ongoing source maintenance.
The repository name does not match the package name and no README mention was collected, so the package-to-source relationship is less transparent; organization backing partly offsets this concern.
Composer build tooling is present, but no security scanning tools were detected, leaving repository security hygiene less transparent.
The repository has no security policy, so it does not document how vulnerability reports should be handled.
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.