Consumer documentation and verification are limited, with no README, tests, or changelog. The MIT declaration and matching repository reduce transparency concerns, but do not offset the thin project evidence.
40%
Total Score
50
61
88
The package has had only one release, published over three years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk.
Only one registry maintainer is listed for this individually backed project. That is not inherently unsafe, but it leaves limited visible publishing redundancy if the maintainer becomes inactive.
The package contains no README, tests, or changelog. Missing tests and changelog are normal in published artifacts, but the absent README matters for a library consumers must integrate.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide little evidence of an active user or contributor community.
Composer is used for the build, which fits the package ecosystem, but no security-scanning tooling is present. This is a modest transparency and maintenance gap rather than a severe 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.