support
How can we help?
Start here. If you're still stuck, we're one email away.
Getting started
Install, run your first scan, read the output.
False positives
Suppress a finding now, then report it so we fix the rule.
Configuration
Limits, trusted authors, entropy thresholds, offline mode.
Custom rules
Detect your own internal token formats.
CI integration
SARIF and GitHub code scanning.
Security issue
Found a vulnerability in Onuri? Report it privately.
Common questions.
Onuri says a secret is in history but I already deleted it
Deleting a file only removes it from the latest commit. Anyone who clones the repo can still read it from history. Treat the secret as leaked: revoke and rotate it first. Rewriting history (for example with git filter-repo) is optional cleanup afterwards, and doesn't help with clones that already exist.
The scan is slow on a huge repo
Use --max-commits N to cap the history walk, --no-history for the working tree only, or --offline to skip dependency lookups. Add generated or vendored folders to .onuriignore.
How do I send a bug report from the app?
Open settings → feedback. You'll see the exact JSON that will be sent before you send it. Diagnostics are only included if you tick the box. If you're offline, the report waits in an outbox and sends later.
Where are my settings stored?
Run onuri config path. On macOS it's ~/Library/Application Support/com.onuri.Onuri/; on Linux, ~/.config/onuri/.
How do updates work?
The app checks onurilabs.com shortly after launch and every few hours. When an update exists, it tells you, and installs only when you click. Every update is signature-checked first.
onuri --version) and OS.