The package has a clear README, matching repository, MIT license, and a documented 1.0.0 release. Maintenance is the main concern: it has had no registry release for about three years and no commits in the last three months, with only one maintainer and no tests or security scanning.
62%
Total Score
50
100
86
100
One registry maintainer is consistent with a small project, but it leaves the package dependent on a single publisher with limited apparent redundancy.
The repository is owned by an individual user rather than an organization, so the single-maintainer and low-activity concerns are not offset by visible organizational backing.
Only one release exists, published about three years ago, with none in the last 12 months; this is a meaningful maintenance concern for a build tool.
The repository recorded no commits and no active maintainers in the last three months, weakening evidence of ongoing maintenance.
Composer is used for builds, but no security scanning tools are present; the missing scanning is a modest transparency gap rather than evidence of abandonment.
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.