lvht/jaeger
Risky to adopt: the package and repository have seen no releases or commits for about eight years, indicating strong abandonment risk. It is licensed, documented, tested, and not deprecated, but those strengths do not offset the lack of ongoing maintenance.
38%
Total Score
0
69
83
Health Score Breakdown
The package has had no releases in the last 12 months, and its latest recorded release was about eight years ago. This is a strong sign that maintenance has stopped.
The repository recorded zero commits and zero active maintainers over the last three months, consistent with the long release gap and indicating no current maintenance capacity.
Composer is used for builds, but no security scanning tools are configured. The lack of scanning is a transparency gap, though it is secondary to the much more significant inactivity.
The repository is not marked archived, which avoids an explicit abandonment signal, but its last push was about eight years ago and does not compensate for the absence of recent activity.
The repository has no security policy. This weakens vulnerability-reporting transparency, although it is less significant than the demonstrated lack of maintenance.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 lvht/jaeger-idl Version ^0.9.0 | — | — |
opentracing/opentracing Version ^1.0.0-beta2 | — | — |
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 8 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.