risk

type FunctionRisk struct {
	Package         string `json:"package"`
	Function        string `json:"function"`
	File            string `json:"file"`
	StartLine       int    `json:"startLine"`
	EndLine         int    `json:"endLine"`
	ExecutableLines int    `json:"executableLines"`
	UncoveredLines  int    `json:"uncoveredLines"`
	Commits         int    `json:"commits"`
	LinesChanged    int    `json:"linesChanged"`
	// Score is commits × uncovered executable lines: no weights, no tuning,
	// both factors visible in the report so the ranking can be argued with.
	Score int `json:"score"`
}

type Options struct {
	Root   string
	Commit string
	Graph  *graph.Graph
	Loader *index.Loader
	// Churn is keyed by slash-separated path relative to Root.
	Churn map[string]vcs.ChurnStat
	// Packages restricts analysis to these import paths; empty means every
	// package in the graph.
	Packages []string
}

type Report struct {
	Functions []FunctionRisk `json:"functions"`
	// CoveredChurning counts churned functions every line of which is covered
	// — change is landing where tests are watching.
	CoveredChurning int `json:"coveredChurning"`
	// UncoveredStable counts functions with uncovered lines in files no commit
	// touched inside the window. Dormant, not safe; below every churning entry
	// in priority.
	UncoveredStable int `json:"uncoveredStable"`
	// Unindexed counts packages none of whose covering test packages have a
	// usable record at this commit. Their functions are invisible to the
	// report, and pretending otherwise would make missing data look like
	// safety.
	Unindexed int `json:"unindexed"`
	// Partial counts packages analyzed with some covering records missing.
	// Coverage can only be under-counted there, so their risk may be
	// overstated — the honest direction, but worth a note.
	Partial  int `json:"partial"`
	Analyzed int `json:"analyzedPackages"`
}