The package is MIT-licensed, has a README, and installs without lifecycle scripts. Its tiny footprint and lack of repository security tooling provide limited transparency, while the repository does not clearly identify or document the package.
52%
Total Score
50
81
83
There has been only one release, published over three years ago, with no releases in the last 12 months. This is a meaningful maintenance concern, although a small utility may be complete after a single stable release.
The repository had no commits and no active maintainers in the last three months. Combined with the single-release history, this increases abandonment risk.
The repository name does not match the package name and its README does not mention the package, so the source relationship is not clearly documented.
Composer build tooling is present, but no security scanning tooling was detected. This is a modest transparency and maintenance gap for a package with otherwise minimal project evidence.
The repository has no security policy. For a small utility this is not severe, but it leaves vulnerability-reporting expectations undocumented.
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.