The package has a clear MIT license, a matching repository, and no install-time scripts. Its only release was published nearly five years ago, with no recent commits and one registry maintainer, making future fixes uncertain. The small, focused artifact limits the practical impact of its missing tests and security policy.
43%
Total Score
50
88
75
One registry account has publish access. That is a thin publishing base for a user-owned project and provides limited evidence of maintenance capacity.
This is the package's only release, published nearly five years ago, with no releases in the last 12 months; the focused package scope softens but does not remove the abandonment concern.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the concern that the project may be abandoned.
Composer is used for the build, which fits the package ecosystem; no security scanning is configured, a minor transparency gap for a dependency.
The repository has no security policy. For a small helper library this is a modest transparency gap rather than a severe dependency risk.
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.