A Base Security Library
45%
Total Score
unhealthy
Risky: long-term inactivity and weak repository-to-package identification outweigh the package's testing and licensing.
The package has only 2 releases, with none in the last 12 months; its latest release was over 4 years ago. This indicates very limited ongoing maintenance.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with a project that has been inactive for over 5 years. That materially raises abandonment risk.
The repository name does not match the package name and its README does not mention the package. While a name mismatch can be normal for a subpackage, the absence of any README reference makes package ownership less clear.
The repository uses Composer build tooling, but no security-scanning tools were detected. For a security-focused library, the missing scanning coverage is a modest transparency and maintenance gap.
No repository security policy was found. The package README gives a direct vulnerability contact, which partly compensates, but the absence of a documented repository process remains a small gap.
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.