Documentation
¶
Overview ¶
Package surface is the core framework for surface mapping (PRD section 10): the language-agnostic home for surface categories and, in Fase 1, the SurfaceQuery format (codefit's own declarative format for enumerating auditable structural surface, distinct from the Semgrep-format rules used for deterministic findings — PRD section 17).
Status: SKELETON. Today it declares the surface categories. The aggregation framework and the SurfaceQuery type and runner are implemented in Fase 1. The per-language enumeration currently lives in each provider's AnalyzeSurface (ADR 0001, provisional); core/surface will host the shared machinery once a second language exists to factor it against.
Index ¶
- func Run(queries []Query, root syntax.Node, file string) []findings.SurfaceItem
- func StableID(file string, line int, category string) string
- func StampIDs(items []findings.SurfaceItem)
- func Summary(category string, enumerated int, in Integration) string
- type Category
- type Confirmation
- type Integration
- type Query
- type Verdict
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
func Run ¶
Run executes each query over the file and returns the union of their items with stable ids stamped. The framework is agnostic: it only orchestrates.
func StableID ¶
StableID derives a short, stable id for a surface item from (file, line, category). It is a PURE function of those three components: the enumeration stamps it on each item, and the confirmation step recomputes it to validate that a verdict refers to a real item — this is what keeps codefit stateless (it stores nothing between enumeration and confirmation, it recomputes).
func StampIDs ¶
func StampIDs(items []findings.SurfaceItem)
StampIDs fills the stable id of any item that does not yet have one. It is idempotent, so emitting boundaries (the sensor, the MCP handler) can call it without caring whether a provider already stamped.
Types ¶
type Category ¶
type Category string
Category is a class of auditable surface the agent reasons about. These match the Category field of findings.SurfaceItem.
type Confirmation ¶
type Confirmation struct {
SurfaceID string `json:"surface_id"`
Category string `json:"category"`
File string `json:"file"`
Line int `json:"line"`
Verdict Verdict `json:"verdict"`
Reasoning string `json:"reasoning"`
Confidence float64 `json:"confidence"`
Severity findings.Severity `json:"severity,omitempty"`
}
Confirmation is what the agent returns after reasoning over a surface item. It carries everything codefit needs to integrate the verdict statelessly: the surface id (revalidated by recomputation) plus the anchor (file/line/category) and the agent's judgment. Severity is optional — the agent, which understands what resource is exposed, judges it; codefit falls back to a class default.
type Integration ¶
type Integration struct {
Findings []findings.Finding
Dismissed []Confirmation
Uncertain []Confirmation
Invalid []Confirmation
}
Integration is the result of folding the agent's verdicts into the report. Each verdict lands in exactly one bucket: Findings (vulnerable, probabilistic), Dismissed (not_vulnerable, kept for traceability, no score impact), Uncertain (flagged for human review — developer autonomy), Invalid (the surface id did not recompute, so the verdict refers to nothing codefit can anchor).
func Integrate ¶
func Integrate(confs []Confirmation) Integration
Integrate folds agent verdicts into the report. It is a pure function of the confirmations passed in — codefit keeps no session. A vulnerable verdict becomes a probabilistic finding (confidence < 1.0 always) anchored to the surface item; the id is revalidated by recomputing StableID.
type Query ¶
type Query interface {
// Enumerate returns the surface items found in the file rooted at root. file
// is the project-relative path (a query may restrict itself by path, e.g.
// Next App Router handlers live in app/**/route.ts).
Enumerate(root syntax.Node, file string) []findings.SurfaceItem
}
Query enumerates the auditable structural surface of one category over a parsed file. Each category+provider implements it; the framework orchestrates queries without knowing any category (it never knows about IDOR or Next).
Source Files