The project has no recent commits or active maintainers, and its repository has no security policy or scanning tools. A README, MIT declaration, matching repository, and release notes help, but they do not offset the long period without maintenance.
38%
Total Score
25
75
83
The package has had only two releases, both within about two days in November 2019, and none in nearly seven years. This strongly indicates abandonment risk.
The repository recorded zero commits and zero active maintainers in the past three months, while its last push was in November 2019. That is the strongest evidence of inactive maintenance.
One registry account has publish access. A single maintainer is a meaningful continuity risk here because the project also shows no recent release or commit activity.
The repository has zero stars, one fork, and one watcher. Low popularity is only supporting evidence, but it offers little indication of a broader user or contributor base to compensate for inactivity.
Composer is used for builds, but no security scanning tools are configured. The missing scanning is a hygiene weakness for a package intended to be installed as a dependency.
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.