Add your projects
Choose the local folders Sieve can read. Inventory stays on your Mac.
Dependency vulnerabilities and exposed credentials, together on your Mac.
New dashboard release preparing for App Review.
Current store version may differ.
Local projects · Saved evidence
Last check: example · Not live project data
Interactive example · synthetic data · no access to your files
Scanning works without AI. Connect an assistant when you want help with the next step.
Choose the local folders Sieve can read. Inventory stays on your Mac.
Opt in to OSV advisory checks. Monitor hourly or every two hours while Sieve is running and your Mac is awake.
See last-check, next-check, and coverage state.
Share saved findings through read-only MCP. Review and approve fixes in your coding tool.
No automatic remediation.
MCP reads saved evidence. It does not grant source-folder access, expose vault values, or apply fixes.
Secret scanning covers supported local AI histories and environment files, including Claude Code, Cursor, VS Code, Windsurf, and Codex formats. Coverage depends on readable files and supported formats. See setup and coverage.
Secret matching, dependency inventory, saved findings, and vault storage.
Public package names and versions go to OSV for advisory checks. Separately enabled MCP shares saved metadata with your assistant and potentially its model provider.
No. Local inventory, secret matching, and advisory checks work without AI. A compatible assistant is optional for interpreting saved evidence and helping you review fixes.
No. Scheduled checks need Sieve running and your Mac awake, with project access and monitoring consent still enabled. Check the last successful check and coverage status before acting.
No. Sieve reports evidence within supported local formats and available advisory coverage. Missing findings are not proof of safety, a disappearing advisory is not a verified fix, and local dependencies may differ from deployed code.
Check the store listing for current availability and pricing.