Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tumban.com/llms.txt

Use this file to discover all available pages before exploring further.

Every completed scan returns a recommendation and a risk_score (0–100). The recommendation is derived from the score:
Score rangeRecommendationSuggested action
0–10no_flagsNo automated signals of violation. Auto-approve unless your policy requires sampling.
11–40review_lowBorderline. Inspect on a capacity-permitting basis.
41–60review_mediumLikely a violation. Send to your review queue.
61–100review_highStrong signals. Priority review.
See Recommendation values for the canonical reference.

​
How the score is produced

Tumban runs three independent detection strategies in parallel and takes the maximum of their scores. A judge model is invoked on borderline aggregated scores (11–70) and may bump the score up or down based on contextual analysis. The score reflects confidence that a violation exists, not uncertainty. Missing data does not raise the score.

​
What no_flags does and doesn’t mean

no_flags means Tumban’s automated analysis did not detect a violation. It does not prove a profile is clean — your manual review process may still catch something the pipeline missed.

​
Integration tips

  • Sort review queues by risk_score descending to triage fastest.
  • Watch for confidence: "low" (more) — those decisions warrant a second look regardless of recommendation tier.
  • Treat completed_with_partial results as actionable but inspect the coverage object first.