How to evaluate community anti-spam without leaking data?

Context: I'm working on mlops 040 and ran into a decision point.

• What I’ve tried: basic setup + quick benchmarks.
• Constraints: limited time, want something stable.

Question: How to evaluate community anti-spam without leaking data?

Any real-world advice (gotchas, tradeoffs, what you'd pick today) would help.