Trixionary Client
40%
Total Score
unhealthy
Risky: no releases or commits since 2016, with 13 open issues and no recent project activity.
The latest release was nearly 10 years ago, with no releases in the last 12 months. Six releases show some prior history, but the long gap strongly indicates abandonment risk.
There were no commits and no active maintainers in the last three months. Combined with the old last release, this is strong evidence that maintenance has stopped.
The repository has 13 open issues and recorded no new or closed issues in the last month. That unresolved backlog adds to the evidence of weak ongoing maintenance.
The repository is not marked archived, so it remains administratively available. However, its last push was nearly 10 years ago, consistent with the inactivity shown by release and commit signals.
The linked repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a transparency gap, though it is less serious than the prolonged inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
gossi/trixionary Version ^0.2 | — | — |
keeko/composer-installer Version * | — | — |
bower-asset/blueimp-file-upload Version ~9 | — | — |
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.