Verify Our Code
SafeMonk is fully open source. Here's how to verify that safemonk.com runs the exact code from our GitHub repository.
Why Code Verification Matters
SafeMonk implements zero-knowledge encryption, meaning your secrets are encrypted in your browser before they ever reach our servers. But how can you trust this claim?
Complete Transparency Through:
- ✓Open Source Code: Our entire codebase is publicly available on GitHub
- ✓Source Maps: Production code can be traced back to the original source
- ✓Reproducible Builds: You can build and run SafeMonk yourself
How to Verify SafeMonk.com Code
Quick Summary
You can verify that safemonk.com runs the exact same code as our GitHub repository by inspecting the source maps in your browser's Developer Tools.
Step 1: Open Developer Tools
Visit safemonk.com and open your browser's Developer Tools:
- Chrome/Edge: Press F12 or Ctrl+Shift+I (Cmd+Option+I on Mac)
- Firefox: Press F12 or Ctrl+Shift+I (Cmd+Option+I on Mac)
- Safari: Press Cmd+Option+I (enable Developer menu first)
Step 2: Navigate to Sources Tab
Click on the "Sources" tab in Developer Tools. You'll see the built application files:
- 📁 www.safemonk.com/
- 📁 _next/ - Next.js compiled files
- 📁 static/ - JavaScript bundles
- 📄 Various .js files - Compiled application code
Note: You'll see compiled JavaScript files, not the original source structure. This is normal for production builds.
Step 3: Verify Encryption Logic
While the production code is compiled, you can verify our security claims by:
1. Network Tab Verification
Open Network tab and create a test secret. You'll see only encrypted data is sent to the server - no plaintext keys or content.
2. Application Tab - Local Storage
Check Application tab → Local Storage. You'll see no encryption keys are stored locally.
3. Compare Source Code
The most reliable verification is comparing our GitHub source code with the compiled application behavior.
Step 4: Compare with GitHub
Compare the code you see in Developer Tools with our GitHub repository:
- 1. Visit our GitHub:github.com/mdotk/safemonk
- 2. Navigate to the same file path (e.g.,
src/lib/crypto.ts) - 3. Compare the code line-by-line
- 4. Verify they are identical ✅
What This Verification Proves
✅ Proves
- • The encryption happens in your browser
- • We cannot see your encryption keys
- • The server only receives encrypted data
- • The code matches our public repository
- • No hidden backdoors or key logging
⚠️ Limitations
- • Requires technical knowledge to verify
- • Cannot prove server-side behavior
- • Assumes your browser is secure
- • Source maps could theoretically differ
Run Your Own SafeMonk Instance
For maximum security and control, you can run your own instance of SafeMonk:
Quick Start
# Clone the repository
git clone https://github.com/mdotk/safemonk.git
cd safemonk
# Install dependencies
npm install
# Set up environment variables
cp env.example .env.local
# Edit .env.local with your Supabase credentials
# Run the development server
npm run dev
# Or build for production
npm run build
npm startJoin Our Open Source Community
SafeMonk is open source and we welcome contributions! Whether you're fixing bugs, adding features, or improving documentation, your help makes SafeMonk better for everyone.