Clear package identity, licensing, documentation, and release notes support adoption. Maintenance depends on one contributor, while the repository has no security policy or scanning tool.
72%
Total Score
50
94
75
The repository is owned by an individual rather than an organization, so the single-contributor concentration is not compensated by visible organizational backing.
One contributor made all 34 recent commits, leaving no demonstrated backup maintainer and creating a meaningful continuity risk for this young project.
The repository recorded 34 commits in the last 3 months, showing substantial recent work, but all activity came from one active maintainer.
Composer build tooling is present, but no security scanning tool was detected, leaving automated dependency or code-health checks unverified.
The repository has no security policy, so there is no documented process for reporting and handling vulnerabilities. This is a transparency gap, not evidence of a vulnerability.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
cuyz/valinor Version ^1.14 | — | — |
dompdf/dompdf Version ^3.0 | — | — |
bacon/bacon-qr-code Version ^3.0 | — | — |
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.