The package has one maintainer and no security scanning, leaving limited ongoing support capacity. Clear documentation, an MIT license, and no install-time scripts reduce adoption and execution concerns.
38%
Total Score
25
79
75
The latest release was published over six years ago, and there have been no releases in the last 12 months. This is strong evidence of abandonment risk despite three total releases.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no visible ongoing maintenance.
A single registry maintainer provides a thin publishing base. The linked repository is user-owned rather than organization-backed, so there is no provided evidence of broader project support.
Composer build tooling is present, but no security scanning tools were detected. That weakens maintenance and review hygiene for a package handling application tracing data.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap, though it is less severe than the inactive maintenance signals.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
openzipkin/zipkin Version ^1.3.4 | — | — |
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.