The repository is small, has no security policy, and provides no automated security scanning. MIT licensing, a working README, and organization backing improve transparency, but ongoing maintenance remains uncertain.
57%
Total Score
75
75
83
The package has 14 releases, but none in the last 12 months; its latest release was about 2 years and 2 months ago. This indicates a maintained history followed by a prolonged pause.
There were 0 commits and 0 active maintainers in the last 3 months. Combined with the old last push, this suggests maintenance has effectively stopped rather than merely slowed.
The repository has 0 stars and 0 forks, with only 3 watchers. Popularity is supporting evidence rather than a verdict, but these figures provide little evidence of broad community oversight.
Composer build tooling is present, but no security-scanning tooling is reported. The missing scanner is a modest transparency and maintenance gap, not evidence of unsafe code.
The linked repository is not archived, although its last push was about 2 years and 2 months ago, which reinforces the maintenance concern shown by the release history.
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.