The MIT license, readable package contents, and organization ownership support transparency. No security policy and no active development reduce confidence in long-term maintenance.
32%
Total Score
50
69
83
This package has only one release, published in September 2017, with no releases in the last 12 months. That long release gap is strong evidence of abandonment for a dependency released as a stable version.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the package's long release inactivity and leaving no evidence of current maintenance.
The repository name does not match this package and its README does not mention the package, creating uncertainty about whether it is the correct source repository rather than a related project repository.
The repository uses Composer build tooling, which fits the package ecosystem, but it has no reported security-scanning tools; this is a modest transparency and maintenance gap.
The repository is not archived, which avoids the strongest abandonment signal, but its last push was in September 2017 and does not offset the absence of recent commits.
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.