COMPARE · NPM PACKAGE
zn vs StackOne Defender
StackOne Defender is the closest thing to zn-gate: an open npm package wrapping tool calls against indirect injection. Here is the honest split.
| Capability | StackOne | zn |
|---|---|---|
| License | Apache-2.0 | MIT (SDKs + Rust core + corpus CC-BY-4.0) |
| Install | npm package, ~22MB, CPU-only | npm/PyPI, 15kB zero-dependency + Rust core |
| Latency | Under 10ms, two-tier | Rules <1ms local · neural ~200ms cloud |
| Indirect injection | Purpose-built for tool results | Yes — tool calls and results inspected |
| Reported accuracy | ~88.7% acc / 90.8% F1 on ~25k samples (self-reported) | v29: EN FPR 0.70% on 4.3k frozen gate |
| Neural layer | No | Yes — multilingual INT8 head (v29) in cloud |
| Evidence ledger | No | SHA-256 chained, verify/export/UI built in |
Pick StackOne when
You only need tool-result screening with the smallest possible footprint, and published F1 on adversarial sets is your buying criterion.
Pick zn when
You want the dual layer (deterministic + neural), multilingual gates, compliance-grade evidence — and a managed cloud path when traffic grows.
← All comparisons · StackOne figures are self-reported by the vendor; ours link from the public corpus.