The package is small, focused, and has clear installation documentation with no runtime dependencies or install scripts. Its long release gap and absent recent development make depending on it a maintenance liability.
46%
Total Score
25
100
81
50
The latest release was about 5 years and 5 months ago, with no releases in the last 12 months and only three releases overall. This is strong evidence of stalled maintenance for a package used in an evolving frontend stack.
The repository has had no commits or active maintainers in the last three months, and its last push was about 3 years and 8 months ago. The non-archived status does not compensate for this prolonged inactivity.
There were no new or closed issues or pull requests in the last month, and no open work is recorded. This is consistent with the release and commit inactivity, although issue counts alone are not decisive.
The repository uses Composer build tooling, but no security-scanning tools were detected. This is a modest transparency and hygiene gap, not evidence that the package is unsafe.
The repository has no security policy. For a small frontend integration module this is a modest transparency gap, but it matters more because there is little recent activity showing how issues would be handled.
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.