Loading HoneyMesh...
Loading HoneyMesh...
Ubuntu App Center beta · AMD64
The Snap you installed provides a terminal command for creating, checking, and simulating Node Guard policies. It has no graphical window or background service. Installing it does not protect your Node.js application; that requires the separate SDK and an application integration.
If you already installed the app in Ubuntu App Center, skip the install line. Otherwise install the beta from a terminal. Run the tools in a normal, non-hidden folder under your home directory; the Snap has the home permission and cannot work with arbitrary system paths.
sudo snap install network-decode-nodeguard --beta
mkdir -p ~/HoneyMesh-NodeGuard
cd ~/HoneyMesh-NodeGuard
network-decode-nodeguard init
network-decode-nodeguard doctor nodeguard.policy.json
network-decode-nodeguard policy validate nodeguard.policy.jsoninit creates nodeguard.policy.json in OBSERVE mode and refuses to overwrite an existing file. doctor should show runtime: supported and policy_mode: OBSERVE. Its source_trust: not checked result is expected: a local CLI cannot verify your app's proxy or real client IP.
The generated policy uses example application and route IDs. Review and replace those values before using it in your own app. No firewall rule or live request limit is created by these commands.
The Snap includes a synthetic observation file. Copy it into your working folder and evaluate it at the fixture's fixed time:
cd ~/HoneyMesh-NodeGuard
cp /snap/network-decode-nodeguard/current/lib/node_modules/@honeymesh/node-guard/examples/auth-observations.json observations.json
network-decode-nodeguard policy test nodeguard.policy.json observations.json --at 2026-11-03T18:00:00ZThe expected result has decision: OBSERVE, hit_count: 2, and restriction_expires_at: null. The simulator reads local JSON only. It sends no packets, changes no firewall settings, and does not activate enforcement.
To evaluate a proposed policy, copy your policy file, change the copy, run policy validate on it, then run policy test with sanitized observations from your app. Keep real credentials and private request data out of these files.
The Snap's policy CLI is currently based on Node Guard 0.2.0-alpha.6. The separately published @network-decode/node-guard npm SDK is at 0.2.0-alpha.12 in our current guide. The SDK runs inside your app, requires Node.js 20 or newer, and has its own policy tools. Use the SDK's version-matched examples and test your policy there before integrating it into a request handler.
cd /path/to/your-node-app
npm install @network-decode/node-guard@0.2.0-alpha.12
npx nodeguard doctor nodeguard.policy.jsonFollow the full SDK manual for verified client IPs, Express and Next.js integration, OBSERVE testing, enforcement, and recovery. Do not assume the Snap and newer npm SDK accept identical policy files without validating them with the version used by your app. The Snap cannot install the SDK into another project for you.
network-decode-nodeguard doctor.snap run network-decode-nodeguard doctor.snap connections network-decode-nodeguard; if home is disconnected, run sudo snap connect network-decode-nodeguard:home.init will not replace it. Review that file or select a new path with init --output new-policy.json.snap info network-decode-nodeguard
sudo snap refresh network-decode-nodeguard --betaThe Snap is an AMD64 beta and runs locally without network or firewall access. It does not install a HoneyMesh agent, attach XDP, share intelligence, or protect an application until its SDK is integrated. See the Snap source and release notes or Node Guard product page.