Hermes plugin install is blocked by benchmark-only scanner findings
Summary
hermes plugins install DietrichGebert/ponytail --enable is blocked as DANGEROUS, although the Hermes runtime plugin itself passes hermes plugins doctor.
Reproduction
Use Ponytail v4.9.0 at commit
2ed6c52c9d7e5e56942508591085fd45dea277d3.Run:
hermes plugins install DietrichGebert/ponytail --ref 2ed6c52c9d7e5e56942508591085fd45dea277d3 --enableHermes reports 93 findings and refuses the install. The critical findings point to benchmark fixtures/examples such as path-traversal strings in
benchmarks/agentic/, rather than the Hermes runtime files (plugin.yaml,__init__.py, andskills/).
Why this matters
The README advertises a Hermes installation path, but cloning the complete repository is rejected before the plugin can be installed. --force does not override a dangerous plugin verdict.
Suggested fix
Could the Hermes distribution be published as a minimal plugin tree (for example, a dedicated directory or repository containing only plugin.yaml, __init__.py, and the required skills/)? This would keep the benchmark suite in the main repository while allowing Hermes to scan the actual runtime payload.
Happy to provide the full scan report if that would help.
Source: DietrichGebert/ponytail