ElicitationResult vs PreToolUse (Write|Edit|MultiEdit|Bash)

Side by side on the facts. GitHub figures come straight from each repository; ratings come from signed-in reviewers here.

MetricElicitationResultHook PreToolUse (Write|Edit|MultiEdit|Bash)Hook

Type: ElicitationResultHook; PreToolUse (Write|Edit|MultiEdit|Bash)Hook
Category: ElicitationResultOther; PreToolUse (Write|Edit|MultiEdit|Bash)Other
GitHub stars: ElicitationResult0; PreToolUse (Write|Edit|MultiEdit|Bash)0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: ElicitationResultNot yet assessed; PreToolUse (Write|Edit|MultiEdit|Bash)Not yet assessed
Community rating: ElicitationResultNo reviews yet; PreToolUse (Write|Edit|MultiEdit|Bash)No reviews yet
Last commit: ElicitationResultUnknown; PreToolUse (Write|Edit|MultiEdit|Bash)Unknown
Licence: ElicitationResultNone declared; PreToolUse (Write|Edit|MultiEdit|Bash)None declared
Official: ElicitationResultNo; PreToolUse (Write|Edit|MultiEdit|Bash)No
Source: ElicitationResult Repository; PreToolUse (Write|Edit|MultiEdit|Bash) Repository

Highlighted cells win that row on an objective measure. Rows without a clear winner — category, licence, source — are left unmarked. A higher trust score means better auditability and maintenance, not safer code.