ttree/eel-nodesearchservice
The small artifact is clearly licensed and has a focused dependency footprint, but its source repository lacks a security policy and does not clearly identify this package. Adoption should account for limited project transparency.
58%
Total Score
75
100
81
83
Health Score Breakdown
Only two releases exist, with the latest published on January 15, 2024—about 2 years and 8 months before collection—and none in the last 12 months. This is a meaningful maintenance concern for a dependency.
There were no commits and no active maintainers in the last 3 months. Combined with the old latest release, this points to a real abandonment risk.
The repository name does not match the package name and its README does not mention the package, so ownership of this source is not clearly established from the collected evidence. The similarly focused file tree offers only limited compensation.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene concern rather than evidence of unsafe code.
The repository has no security policy. For a small helper library this is a transparency gap, though it is less severe than missing maintenance or an archived project.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 neos/neos Version ^3.0 || ^4.0 || ^5.0 || ^7.0 || ^8.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 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.