The package is documented, licensed, and backed by an organization, with tests in the repository. Its workflow uses nine unpinned actions, adding supply-chain hygiene risk.
62%
Total Score
67
100
81
50
The package has had no registry releases in the last 12 months, and its latest release was about 2 years and 10 months ago. This weakens confidence in ongoing release maintenance despite the repository being updated more recently.
There were no commits and no active maintainers in the last 3 months. This suggests current development has slowed, although the repository's more recent push prevents treating it as abandoned outright.
The repository has four open issues and four open pull requests, but no new or closed issues or pull requests in the last month. The backlog and lack of recent resolution indicate limited visible project activity.
Composer build tooling is present, but no security-scanning tool was detected. This is a transparency and hygiene gap, not evidence that the release is unsafe by itself.
The repository has no security policy. For a terminal-control library this reduces the clarity of vulnerability reporting and response expectations, though no other provided signal shows an active security issue.
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.