The tiny three-character README and absent security policy leave little consumer or project transparency. MIT licensing and a small dependency footprint are positives, but the install-time script deserves care.
30%
Total Score
0
100
64
50
The package has only one release, with no releases in about 10 years. That strongly suggests abandonment and outweighs the absence of a formal deprecation notice.
The repository recorded zero commits and zero active maintainers in the last 3 months, with its last push about 10 years ago. This is strong evidence that maintenance has stopped.
The package runs a post-create-project-cmd lifecycle script. Such scripts can be appropriate for a project template, but they add install-time behavior that consumers should inspect before adoption.
A README is present but contains only 3 characters, offering essentially no usage guidance. Missing tests and a changelog in the package artifact are normal packaging practice and are not counted against it.
The repository has 0 stars, 0 forks, and 1 watcher. Popularity is only supporting evidence, but these values provide no meaningful community or adoption buffer for the long maintenance gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
loopsframework/base Version * | — | — |
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.