Submit: jep-snap - JEP Guard

### Snap Submission

**Name:** JEP Guard

**Description:** Protect your assets from malicious transactions with verifiable JEP receipts. JEP Guard analyzes transaction risk, shows confirmation dialogs, and generates cryptographically verifiable receipts for every transaction.

**npm Package:** jep-snap

**Version:** 0.1.0

**Repository:** https://github.com/hjs-eth/jep-snap

**Category:** Security

**Tags:** security, protection, audit, jep, metamask, transaction-protection

### Why this Snap?
- Detects high-risk transactions before you sign
- Shows clear warnings with risk levels (low/medium/high)
- Generates JEP receipts as verifiable evidence
- Stores all receipts locally in MetaMask
- Based on IETF Internet-Draft standard

### Checklist
- [x] My Snap is published on npm
- [x] My Snap works with MetaMask Flask
- [x] I have tested the Snap locally
- [x] README includes clear installation instructions
- [x] I have read the submission guidelines

### Additional Information
This Snap uses the JEP (Judgment Event Protocol) which has been submitted as an IETF Internet-Draft: https://datatracker.ietf.org/doc/draft-wang-hjs-judgment-event/

Start by reviewing the jep-snap repository and npm package linked in the submission, then compare the provided checklist and JEP details with the directory's submission requirements. Done would require a clear decision about whether this Snap is ready for inclusion, but the issue does not name a directory file, test, or concrete implementation change.

Written by the indexing model from the issue text.