A clear license, readable documentation, and tests improve day-to-day adoption. Maintenance depends heavily on one contributor, and the linked repository does not identify this package in its name or README.
70%
Total Score
50
88
75
Only one registry account has publish access. The recent release cadence provides some compensation, but publishing and continuity remain concentrated.
The repository is owned by an individual user rather than an organization, so the single-contributor and single-publisher concentration is not buffered by visible organizational backing.
One contributor made all recent commits, leaving maintenance concentrated in a single person. The regular release history partly offsets this but does not remove the continuity risk.
Only one commit was recorded in the last 3 months, despite the recent registry releases; this suggests limited observed development activity.
The repository name does not match the package name and its README does not mention the package, so the package-to-source relationship is less transparent than expected.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
bain2018/think-installer Version ^3.1 | — | — |
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.