The workflow uses three unpinned actions, and the repository has no security policy or security-scanning tools. Clear licensing, tests in the repository, a substantial README, and no install-time scripts reduce adoption friction.
68%
Total Score
50
100
86
67
The package and repository are owned by the same individual account, so the identity linkage is clear, but there is no organizational backing shown by this signal.
The package was first released today and has four releases within the same day, so there is no demonstrated maintenance history yet. The rapid releases show active initial work but do not establish long-term reliability.
There were no commits and no active maintainers in the measured three-month window, but the package and repository were created today, making this primarily an absence of history rather than evidence of a collapsed project.
Composer build tooling is present, but no security-scanning tools are configured. This is a modest transparency and maintenance gap, not evidence that the release is unsafe.
The repository has no security policy, leaving vulnerability reporting and disclosure expectations undocumented for a package intended for application integration.
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.