MIT licensing, a README, tests, and no install-time scripts make adoption easier to inspect. The single-user project has no security policy or automated security scanning, so independent assurance is limited.
48%
Total Score
50
81
83
Only two releases were published, both in June 2023, with no releases in the last 12 months. This is a substantial maintenance concern for a package with a current v0.2.0 release.
There were no commits and no active maintainers in the last three months, consistent with the repository's last push in June 2023. This leaves current maintenance capacity unverified.
Composer build tooling is present, but no security scanning tools are configured. That weakens repository assurance, although it does not by itself show abandonment.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities in a security-sensitive proxy library.
The latest release is v0.2.0 rather than a stable major release, which signals limited maturity. The package is not marked as a prerelease, providing only modest compensation.
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.