Support
We're here to help. Most issues are resolved quickly.
Contact
Email us at gautamumapathy@gmail.com and we'll reply within 24–48 hours.
Frequently Asked Questions
What is new in the dependency dashboard?
The new release combines secret findings and saved dependency advisories in a severity-colored overview. Add a supported local project, review its package inventory, and explicitly allow an OSV advisory check. The release is being prepared for App Review; features may differ from the currently published App Store version.
How fresh are project findings?
Enable hourly or two-hour monitoring separately for each project to allow scheduled OSV requests. Sieve must be running and your Mac awake. Check the displayed last-check, next-check, and coverage state; a failed check retains earlier evidence rather than showing a misleading zero. Local project results do not establish what version is deployed online.
Can my AI assistant read the dependency findings?
Enable MCP and separately enable project snapshot sharing, then use Sieve's connection instructions for your compatible client. Sharing exposes saved project names, relative manifest paths, package versions, and advisory evidence to that client and potentially its model provider. It does not grant source-folder access or permission to fix code. Vault execution remains a separate permission.
Why doesn't Sieve show any findings?
A few things to check:
- Make sure you've granted access to at least one AI tool folder in the Grant Access sheet (first launch) or via the sandbox bookmark.
- Tap the scan button (▶ icon, top right) to trigger a fresh scan after granting access.
- If the AI tool folder is empty or you haven't used the tool yet, there's nothing to find — that's a good thing.
The Vault says "Keychain entitlement missing"
This happens when running an unsigned or CLI build. Run Sieve from the signed Mac app (the .app in Applications). If you installed from the App Store, make sure you're launching the App Store version, not a debug build.
Touch ID isn't appearing when I copy from Vault
If your Mac doesn't have Touch ID, macOS will use your login password instead — this is expected. If neither appears, check that Sieve has the Keychain entitlement (this is only an issue in debug builds).
Can Sieve read my secrets?
Sieve must read selected files locally to detect secrets. It stores redacted finding metadata and HMAC fingerprints, not raw secret values, in the findings database. Vault values are stored in macOS Keychain and require macOS authentication for sensitive access. Optional dependency advisory requests do not include secret values.
How do I add the MCP server to Claude Code?
Enable MCP in Sieve's Settings tab, then copy the configuration snippet shown there and paste it into your ~/.claude.json. Restart Claude Code. The MCP toggle must stay enabled while you're using it.
How do I reset everything?
- Findings only: Delete
~/Library/Application Support/Sieve/sieve.db - Vault only: Use "Reset Vault" button in the Vault tab (requires confirmation)
- Complete reset: Delete the app and
~/Library/Application Support/Sieve/
What AI tools does Sieve scan?
- Claude Code —
~/.claude/ - Cursor —
~/Library/Application Support/Cursor/ - VS Code (Copilot) —
~/Library/Application Support/Code/ - VS Code Insiders —
~/Library/Application Support/Code - Insiders/ - Windsurf —
~/Library/Application Support/Windsurf/ - Codex —
~/.codex/ - Project .env files — any directory you add in Settings
Also check out Vibe Scan
For scanning publicly deployed web apps for exposed secrets, try vibe-scan.app — great for checking your own vibe-coded apps before sharing them.