The package has a clear README, tests, a matching repository, and a minimal dependency profile. Its only release was in January 2017, with no recent commits or release activity, and it lacks a security policy; treat it as an experimental, largely unmaintained dependency.
52%
Total Score
50
100
81
50
The repository is owned by an individual user rather than an organization. That is consistent with a small project but provides limited evidence of sustained institutional backing.
There has been only one release, published about 9 years ago, with no releases in the last 12 months. This strongly limits evidence of ongoing maintenance.
There were zero commits and zero active maintainers in the last 3 months. Combined with the single-release history, this is meaningful evidence of inactive maintenance.
Composer is used for the build, but no security scanning tools are configured. This is a modest transparency and maintenance gap, not a severe risk by itself.
The repository has no security policy. For a small library this is a transparency gap, though the available tests and repository license provide some compensating project structure.
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.