The small codebase and simple dependency set reduce complexity. Documentation, security transparency, and community traction are thin, leaving meaningful abandonment risk.
38%
Total Score
50
100
72
50
The package has had only two releases, both in March 2018, and none in about eight years. That long period without a release is strong evidence of abandonment risk, despite the stable 1.0.1 version.
The published artifact has no README, tests, or changelog, and the linked repository also reports no tests or changelog. Missing tests and changelog are not expected in every published artifact, but the absent README weakens consumer transparency for a library.
The repository is owned by an individual user rather than an organization. This does not prove poor maintenance, but it provides limited visible backing when combined with the stale activity and minimal community traction.
The repository has one star, zero forks, and one watcher, indicating very limited visible adoption or community support. Popularity is only supporting evidence, but this reinforces the maintenance concern.
Composer is used as the build tool, but no security scanning tool is reported. The missing scanning is a transparency and hygiene gap rather than evidence of unsafe code.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
league/flysystem Version ^1.0 | — | — |
keven/instantiator Version ^1.0 | — | — |
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.