Trust & Transparency
We understand that feeding your secrets through any tool requires trust. This page explains exactly what Mantle does with your data.Your Secrets Never Leave Your Machine
Here’s exactly what happens when you rundotset mantle run:
- Secrets are read from your providers (
.env, AWS SM, environment variables) - Values are held in-memory during command execution only
- Output streams are scanned for these values and redacted
- After exit, secret values are garbage collected — never written to disk
What is NOT Collected
| Data | Collected? | Reason |
|---|---|---|
| Secret values | ❌ Never | Processed locally only |
| Secret names/keys | ❌ Never | Not needed |
| Build log contents | ❌ Never | Redaction happens locally |
| Source code | ❌ Never | We never access your code |
.env file contents | ❌ Never | Read locally, never transmitted |
100% Local Operation
Mantle is designed to work 100% locally. No cloud connection is required:| Feature | Works Offline? |
|---|---|
| Secret redaction | ✅ Yes |
.env file loading | ✅ Yes |
| Protection modes (detect/redact/block) | ✅ Yes |
| HTML report generation | ✅ Yes |
| All CLI features | ✅ Yes |
Open Source & Auditable
The entire Mantle CLI is open source under the MIT license. You can:View Source Code
Full source on GitHub
Build From Source
Clone and build locally instead of using npm
Report Issues
Security issues welcome via responsible disclosure