PostToolUse (apply_patch|Edit|Write) vs PreToolUse

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

MetricPostToolUse (apply_patch|Edit|Write)Hook PreToolUseHook

Type: PostToolUse (apply_patch|Edit|Write)Hook; PreToolUseHook
Category: PostToolUse (apply_patch|Edit|Write)Other; PreToolUseOther
GitHub stars: PostToolUse (apply_patch|Edit|Write)0; PreToolUse0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: PostToolUse (apply_patch|Edit|Write)Not yet assessed; PreToolUseNot yet assessed
Community rating: PostToolUse (apply_patch|Edit|Write)No reviews yet; PreToolUseNo reviews yet
Last commit: PostToolUse (apply_patch|Edit|Write)Unknown; PreToolUseUnknown
Licence: PostToolUse (apply_patch|Edit|Write)None declared; PreToolUseNone declared
Official: PostToolUse (apply_patch|Edit|Write)No; PreToolUse Yes
Source: PostToolUse (apply_patch|Edit|Write) Repository; PreToolUse 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.