PreToolUse (__exec$) vs PreToolUse (Write|Edit|MultiEdit)

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

MetricPreToolUse (__exec$)Hook PreToolUse (Write|Edit|MultiEdit)Hook

Type: PreToolUse (__exec$)Hook; PreToolUse (Write|Edit|MultiEdit)Hook
Category: PreToolUse (__exec$)Other; PreToolUse (Write|Edit|MultiEdit)Other
GitHub stars: PreToolUse (__exec$)0; PreToolUse (Write|Edit|MultiEdit)0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: PreToolUse (__exec$)Not yet assessed; PreToolUse (Write|Edit|MultiEdit)Not yet assessed
Community rating: PreToolUse (__exec$)No reviews yet; PreToolUse (Write|Edit|MultiEdit)No reviews yet
Last commit: PreToolUse (__exec$)Unknown; PreToolUse (Write|Edit|MultiEdit)Unknown
Licence: PreToolUse (__exec$)None declared; PreToolUse (Write|Edit|MultiEdit)None declared
Official: PreToolUse (__exec$)No; PreToolUse (Write|Edit|MultiEdit)No
Source: PreToolUse (__exec$) Repository; PreToolUse (Write|Edit|MultiEdit) 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.