The package includes substantial documentation and tests, with active recent development by two contributors. Its security process is less transparent because no security policy or scanning tools were found, but the release is licensed, non-deprecated, and free of install-time scripts.
82%
Total Score
80
94
83
Only one registry account can publish the package, which is a modest publishing single point of failure. The repository evidence of two active contributors partly compensates for that limitation.
The repository is owned by a user account rather than an organization, so the small contributor base is not supported by visible organizational backing.
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and process gap rather than evidence of unsafe code.
The repository has no security policy, leaving reporting and response expectations undocumented. This lowers transparency for a package that instruments application requests and integrations.
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.