yxpil
10 MCP servers associated with this publisher in public records · generated 2026-10-05T00:17:46.523Z
incomplete 10 Findings medium 1
Records
| Server | Verdict | Package | Findings |
|---|---|---|---|
| github.com/yxpil/adonword | incomplete | — | 0 finding(s) |
| github.com/yxpil/firelin | incomplete | — | 0 finding(s) |
| github.com/yxpil/howcueme | incomplete | — | 0 finding(s) |
| github.com/yxpil/memorypool | incomplete | — | 0 finding(s) |
| github.com/yxpil/neton | incomplete | — | 0 finding(s) |
| github.com/yxpil/panoptes | incomplete | — | 0 finding(s) |
| github.com/yxpil/pilinstaller | incomplete | — | 0 finding(s) |
| github.com/yxpil/pilseocore | incomplete | — | 0 finding(s) |
| github.com/yxpil/secforge | incomplete | — | 0 finding(s) |
| github.com/yxpil/tentacletool | incomplete | — | 1 finding(s), 1 above info |
Scope
Data comes from public registry entries and manifests of packages that were actually published. Each row opens a standalone evidence page.
Repository source is outside this index’s scan scope. Run the CLI locally for source scanning.
A finding is a matched shape, not a conclusion. It does not prove exploitability. Unmeasured work is listed on each server page and is never treated as clean.