The scanner library.
Choose the object you need to inspect. These ten guides distinguish scanning interfaces, API security testing, AI evaluation, code review, file analysis, and image intelligence.
Scanner API
Scan orchestration · Result design · Review workflows
02AI Scanner
Evaluation · Confidence · Human review
03API Scanner
Endpoint inventory · Authorization · Safe testing
04AI LLM Scanner API
Prompt injection · Retrieval · Tool boundaries
05Git Repo Scanner
Secrets · Code findings · Dependency context
06Antivirus Scanner API
Engine integration · Updates · Quarantine
07Malware Scanner API
Analysis jobs · Engine evidence · Triage
08File Scanner API
Upload validation · Type inspection · Storage policy
09Reverse Image Scanner
Image matching · Source context · Similarity
10EXIF Data Scanner
Metadata · Privacy · Provenance limits
What are you inspecting?
For application permissions, choose API scanning. For credentials or source findings, choose repository scanning. For uploaded content, start with file scanning and add antivirus or malware analysis according to the workflow.
For model-assisted decisions, begin with AI evaluation. For a language-model application, extend the review to retrieval and tool boundaries. For visual material, separate matching against an index from reading the metadata in the file.
What happens next?
A scanner result can support routing, investigation, quarantine, or release. Define the action before choosing the integration. The evidence needed to prioritize a review queue may not be enough to approve a public download.
Keep incomplete coverage visible. An unsupported format, failed engine, or missing input should remain a distinct outcome with an owner and a next step.
Explore the shared integration patternKnow what
you’re scanning.
Find the right guide for your input, your workflow, and the decision that comes next.