The lone maintainer and absent security policy leave little visible capacity for support or response. The MIT license, compact artifact, and release notes improve transparency, but the repository does not clearly identify this package.
32%
Total Score
25
67
75
Only one release was published, on January 23, 2017, with no releases in the last 12 months; this is strong evidence of abandonment risk.
The repository has had zero commits and zero active maintainers in the last three months, consistent with the long release gap and showing no current maintenance.
One registry maintainer is a thin support base for a user-owned project, leaving little observable redundancy if that maintainer stops responding.
The repository name does not match the package name and its README does not mention the package, so the link between the published artifact and source is unclear.
Composer build tooling is present, but no security scanning tools were detected; this is a modest hygiene gap rather than evidence of unsafe behavior by itself.
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.