Usable with caveats: the package is licensed, tested, documented, and backed by an active-looking organization-owned repository, but the latest release was in April 2021 and there has been no commit activity in the last three months. Depend on it only if its older code and compatibility meet your needs.
58%
Total Score
75
100
88
80
The package has 14 releases since December 2018, but it has had no registry release in the last 12 months and its latest release was April 2021. That long release gap is a meaningful maintenance concern.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old registry release, this substantially raises the risk that fixes or compatibility updates may not arrive.
There are only two open issues and no pull requests, with no issue or pull-request activity in the last month. This is consistent with a quiet project and offers little evidence of current responsiveness.
The repository uses Composer build tooling, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap, not a severe risk by itself.
No repository security policy was found. For a small command-line client this is a transparency gap, but it does not by itself indicate that the package is unfit to use.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
luyadev/luya-core Version ^1.0|^2.0 | — | — |
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.