Its four-file package and single-person ownership provide little evidence of engineering depth. The MIT declaration, focused README, and non-deprecated status help, but there is no security policy or scanning to support ongoing confidence.
35%
Total Score
25
75
50
The package has had only 5 releases, with no releases in the last 12 months, despite being nearly 8 years old. This is strong evidence of abandonment risk; the stable release pattern does not compensate for the prolonged inactivity.
The repository recorded 0 commits and 0 active maintainers over the last 3 months, consistent with its last push occurring nearly 8 years ago. This sharply reduces confidence that defects or compatibility issues will be addressed.
One registry maintainer is a thin support base for a user-owned project. No organizational backing is shown to compensate for that concentration of responsibility.
The package contains only 4 files, including two source files and a README, indicating a narrowly scoped implementation. Its small size may limit maintenance burden, but it also provides little evidence of mature project structure.
Composer is used for the build, which is appropriate for a Packagist package, but no security-scanning tools are present. The lack of scanning is a minor hygiene concern rather than proof of unsafe code.
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.