Skip to content
DashboardWebsite

Generic fallback pack

Pack name: generic

The generic pack reviews content when auto-routing finds no enabled dedicated pack to handle it. It treats the content as opaque text and does not parse a specific format. See auto-routing for how the router selects packs.

The router excludes generic from normal file_globs matching and sniff() confidence scoring. Its file_globs list is empty, and it uses the base sniff() default of 0.0. The router uses it only in explicit fallback branches, when the pack is enabled for the analysis target and no enabled dedicated pack claims the content.

A routed Detection has fallback: true. This lets callers distinguish fallback routing from a dedicated pack match.

The pack treats the entire input as one opaque unit. It names the unit after the first non-blank line, truncated to 80 characters. If the input contains no non-blank line, it uses (blob). The unit’s type and action are both "unknown".

The pack’s rule file is rules/generic.md. It asks the LLM to flag issues that a careful reviewer could identify without knowing the content’s format:

  • Hardcoded secrets, destructive operations, wide-open access control, and obvious syntax errors.
  • Obvious performance or reliability problems, such as network calls without a timeout, unbounded retries, or a query or network call repeated for each item in a loop. These should be LOW or MEDIUM severity.
  • Unsafe calls or patterns identifiable by name or shape: memory-unsafe C calls (gets, or strcpy and memcpy with no visible bound), untrusted input passed to an execution sink (exec(, system(, SQL built from strings), unsafe deserialization of non-literal data (pickle.loads, unsafe yaml.load), and security controls visibly turned off, such as TLS verification off or an empty exception handler. The LLM recognizes these by name, not by identifying the language.
  • Credentials or personal data in debug output, and internal URLs paired with credentials.

The rules prohibit format-specific assumptions and subjective style findings. They cap finding confidence at MEDIUM, because the pack has no ground truth for what correct content looks like. If no issue qualifies, the LLM should return no finding and recommend building a dedicated pack.

An org admin can enable or disable generic with the per-org installed-pack setting. If it is disabled for the analysis target, the router does not use it as a fallback. Unmatched content remains unassigned, and the detection reports that no pack is available.

If this pack regularly handles a particular content type, build a dedicated pack for it. See Adding a Pack.