The package has a clear README, a matching source repository, a small dependency surface, and release notes for this version. Missing security scanning and a security policy reduce transparency for a package handling message data.
43%
Total Score
0
71
75
The package has had no release in nearly five years: six releases were published overall, but none appeared in the last 12 months. This is strong evidence of abandonment risk despite the short early release intervals.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving maintenance capacity unproven.
The repository has only 2 stars, 1 fork, and 1 watcher. Low popularity is supporting evidence rather than decisive on its own, but it provides little compensating community signal for the dormant project.
Composer build tooling is present, but no security scanning tools are configured. The missing scanning reduces supply-chain maintenance transparency, although it does not by itself show a defect in the release.
The repository has no security policy, which weakens the process for reporting and handling issues in a package that processes workplace messages. This is a transparency gap, but not severe on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
azhida/tools Version ^0.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.