AI Slop Code Risk Monitor

authzed/spicedb

SlopCodeMonitor badge for authzed/spicedb Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Open Source, Google Zanzibar-inspired database for scalably storing and querying fine-grained authorization data

1.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for authzed/spicedb, a Go project with 7,183 GitHub stars. SynthScan examined 342,917 lines of code across 1489 source files, recording 318 pattern matches distributed across 9 syntactic categories. The legacy adjusted pattern signal is 1.4 (Low pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

1.4
Adjusted Signal
1.4
Raw Pattern Score
100%
Time Factor
2026-10-30
Last Push
7.2K
Stars
Go
Language
342.9K
Lines of Code
1.5K
Files
318
Pattern Hits
2026-10-31
Scan Date
0.00
HC Hit Rate

Risk Review · Payload v1

Use each vector to guide manual verification of the underlying findings.

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 5.4/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 293 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

Are imports declared and package/API names verified? 0 finding(s).

Agent Over-Engineering Ratio 1.7/100 · LOW

Are wrappers, guards, and repeated structures necessary? 39 finding(s).

PR Review Velocity Impact 5.2/100 · LOW

Which changes need focused human review? 318 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 0MEDIUM 26LOW 292

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 318 distinct pattern matches across 9 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Over-Commented Block167 hits · 163 pts
SeverityFileLineSnippetContext
LOW…memoryprotection/memory_protection_integration_test.go41 // to be off for the server to start at all here. AvailableMemory() isCOMMENT
LOWinternal/middleware/perfinsights/doc.go1// Package perfinsights defines middleware that reports the latency of API calls to Prometheus.COMMENT
LOWinternal/middleware/perfinsights/perfinsights.go41 string(FilterLabel),COMMENT
LOWinternal/testserver/datastore/datastore.go21 // never succeeded.COMMENT
LOWinternal/testserver/datastore/datastore.go41// database/service, expressly for testing.COMMENT
LOWinternal/dispatch/executor.go461 }, nilCOMMENT
LOWinternal/dispatch/graph/graph.go561 }COMMENT
LOWinternal/dispatch/keys/computed.go141COMMENT
LOWinternal/datasets/basesubjectset.go21// to the base implementation.COMMENT
LOWinternal/datasets/basesubjectset.go381 // sets.COMMENT
LOWinternal/datasets/basesubjectset.go541 // the resulting concrete subjects are {user:tom, user:amy} because the first set containsCOMMENT
LOWinternal/datasets/basesubjectset.go561 ),COMMENT
LOWinternal/datasets/basesubjectset.go661COMMENT
LOWinternal/graph/check.go81 // For example, a check of resources `user:{tom,sarah,fred}` and subject `user:sarah` willCOMMENT
LOWinternal/graph/lookupsubjects.go641 // For example, given relationships which formed the dispatch:COMMENT
LOWinternal/graph/lookupresources3.go101COMMENT
LOWinternal/graph/lookupresources3.go121//COMMENT
LOWinternal/graph/lookupresources3.go141// │ │ │ │ │ #1 │ │ #2 │ │ #N │ │ │ │COMMENT
LOWinternal/graph/lookupresources3.go161// For each entrypoint, implements a producer-mapper pattern:COMMENT
LOWinternal/graph/lookupresources3.go181// │ └──────────────────┘ │ │ Dispatch to │ │ │COMMENT
LOWinternal/graph/lookupresources3.go201// - Example: document#read = viewer + parent->readCOMMENT
LOWinternal/graph/lookupresources3.go221// # Cursor ManagementCOMMENT
LOWinternal/graph/lookupresources3.go801 skipCaveats := !possibleTraits.AllowsCaveatsCOMMENT
LOWinternal/graph/computed/computecheck.go21 // NoDebugging indicates that debug information should be retainedCOMMENT
LOWinternal/namespace/canonicalization.go21// it into a Binary Decision Diagram (BDD) via the `rudd` library.COMMENT
LOWinternal/namespace/canonicalization.go41// relation second: ...COMMENT
LOWinternal/cursorediterator/doc.go1// Package cursorediterator provides a series of specialized iterator builders that supportCOMMENT
LOWinternal/cursorediterator/blocks.go21var cursorsDisabledKey = ctxkey.NewBoxedWithDefault(false)COMMENT
LOWinternal/cursorediterator/blocks.go141 // Otherwise, we call the `header` iterator with the nextStartingIndex, and then returnCOMMENT
LOW…rnal/datastore/benchmark/postgres_delete_bench_test.go21 "github.com/authzed/spicedb/pkg/datastore"COMMENT
LOWinternal/datastore/proxy/optimized_revision.go21// singleflighted computation of the optimized revision.COMMENT
LOWinternal/datastore/proxy/optimized_revision.go41// after a failed shared attempt. The retry runs on the caller's own context, soCOMMENT
LOWinternal/datastore/proxy/checkingreplicated.go41// NewCheckingReplicatedDatastore creates a new datastore that writes to the provided primary and readsCOMMENT
LOWinternal/datastore/proxy/poolsim/poolsim.go1// Package poolsim provides a datastore proxy that models a fixed-size databaseCOMMENT
LOWinternal/datastore/proxy/indexcheck/indexcheck.go21 return &indexcheckingProxy{delegate: delegate, explainable: explainable}COMMENT
LOWinternal/datastore/proxy/schemacaching/hitrate_test.go81//COMMENT
LOWinternal/datastore/crdb/partitioner.go21// have columns in a different order than the PK, producing partition boundsCOMMENT
LOWinternal/datastore/crdb/partitioner.go141COMMENT
LOWinternal/datastore/crdb/schema_chunker.go21// executing, so that bytea parameters and results use the binary format.COMMENT
LOWinternal/datastore/crdb/schema_chunker.go41// which in effect halves the largest schema SpiceDB can store on CRDB. Note thatCOMMENT
LOWinternal/datastore/crdb/crdb.go101 //COMMENT
LOWinternal/datastore/crdb/options.go121 computed.writePoolOpts.ConnMaxLifetimeJitter = ptr.To(30 * time.Minute)COMMENT
LOWinternal/datastore/crdb/options.go141// held by the application very frequently.COMMENT
LOWinternal/datastore/crdb/options.go161// The health-check may not be able to clean up those connections if they areCOMMENT
LOWinternal/datastore/crdb/options.go181// idle connection) before considering that connection unhealthy and discardingCOMMENT
LOWinternal/datastore/crdb/options.go221// WriteConnMaxLifetime is the duration since creation after which a writeCOMMENT
LOWinternal/datastore/crdb/options.go241//COMMENT
LOWinternal/datastore/crdb/ttl_changefeed.go21// supportsTTLChangefeedReplicationParam returns whether the connected CockroachDBCOMMENT
LOWinternal/datastore/crdb/pool/pgx.go21// distribute, sublicense, and/or sell copies of the Software, and toCOMMENT
LOWinternal/datastore/crdb/pool/node_id.go1package poolCOMMENT
LOWinternal/datastore/crdb/pool/node_id.go21// standalone (non-multitenant) CockroachDB nodes.COMMENT
LOWinternal/datastore/crdb/pool/node_id.go41// +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+COMMENT
LOWinternal/datastore/postgres/replica_lag_test.go21 pgmigrations "github.com/authzed/spicedb/internal/datastore/postgres/migrations"COMMENT
LOWinternal/datastore/postgres/options.go141func ReadStrictMode(readStrictMode bool) Option {COMMENT
LOWinternal/datastore/postgres/options.go161// This value defaults to 30s.COMMENT
LOWinternal/datastore/postgres/options.go181//COMMENT
LOWinternal/datastore/postgres/options.go241//COMMENT
LOWinternal/datastore/postgres/revisions_test.go221}COMMENT
LOWinternal/datastore/postgres/postgres_shared_test.go41// constructors in this package. See test.DisableBackgroundGC for what it means.COMMENT
LOWinternal/datastore/postgres/postgres_shared_test.go1021}COMMENT
107 more matches not shown…
Decorative Section Separators25 hits · 101 pts
SeverityFileLineSnippetContext
MEDIUM⚡internal/graph/lookupresources3.go129// ┌──────────────────────────────────────────────────────────────────────────────┐COMMENT
MEDIUM⚡internal/graph/lookupresources3.go131// ├──────────────────────────────────────────────────────────────────────────────┤COMMENT
MEDIUM⚡internal/graph/lookupresources3.go133// │ ┌─────────────────┐ ┌──────────────────────────────────────────────────┐ │COMMENT
MEDIUM⚡internal/graph/lookupresources3.go136// │ │ │ │ ┌─────────────────────────────────────────────┐ │ │COMMENT
MEDIUM⚡internal/graph/lookupresources3.go139// │ │ │ │ │ │ ┌──────────┐ ┌──────────┐ ┌──────────┐ │ │ │COMMENT
MEDIUM⚡internal/graph/lookupresources3.go140// │ └─────────────────┘ │ │ │ │Entrypoint│ │Entrypoint│ │Entrypoint│ │ │ │COMMENT
MEDIUM⚡internal/graph/lookupresources3.go142// │ │ │ │ └──────────┘ └──────────┘ └──────────┘ │ │ │COMMENT
MEDIUM⚡internal/graph/lookupresources3.go144// │ │ │ └─────────────────────────────────────────────┘ │ │COMMENT
MEDIUM⚡internal/graph/lookupresources3.go146// │ │ │ ┌─────────────────────────────────────────────┐ │ │COMMENT
MEDIUM⚡internal/graph/lookupresources3.go149// │ │ │ └─────────────────────────────────────────────┘ │ │COMMENT
MEDIUM⚡internal/graph/lookupresources3.go150// │ │ └──────────────────────────────────────────────────┘ │COMMENT
MEDIUM⚡internal/graph/lookupresources3.go152// │ └──────────────────┬────────────────────────────────────┘COMMENT
MEDIUM⚡internal/graph/lookupresources3.go154// │ ┌─────────────────────┐ │COMMENT
MEDIUM⚡internal/graph/lookupresources3.go158// │ └─────────────────────┘ │COMMENT
MEDIUM⚡internal/graph/lookupresources3.go159// └──────────────────────────────────────────────────────────────────────────────┘COMMENT
MEDIUM⚡internal/graph/lookupresources3.go165// ┌─────────────────────────────────────────────────────────────────────────────┐COMMENT
MEDIUM⚡internal/graph/lookupresources3.go167// ├─────────────────────────────────────────────────────────────────────────────┤COMMENT
MEDIUM⚡internal/graph/lookupresources3.go169// │ ┌─────────────────┐ ┌──────────────────┐ ┌──────────────────────┐ │COMMENT
MEDIUM⚡internal/graph/lookupresources3.go173// │ │ • Relation EP │ │ │ │ ┌──────────────────┐ │ │COMMENT
MEDIUM⚡internal/graph/lookupresources3.go177// │ └─────────────────┘ │ │ │ └──────────────────┘ │ │COMMENT
MEDIUM⚡internal/graph/lookupresources3.go180// │ │ │ │ ┌──────────────────┐ │ │COMMENT
MEDIUM⚡internal/graph/lookupresources3.go181// │ └──────────────────┘ │ │ Dispatch to │ │ │COMMENT
MEDIUM⚡internal/graph/lookupresources3.go184// │ │ └──────────────────┘ │ │COMMENT
MEDIUM⚡internal/graph/lookupresources3.go185// │ └──────────────────────┘ │COMMENT
MEDIUM⚡internal/graph/lookupresources3.go186// └─────────────────────────────────────────────────────────────────────────────┘COMMENT
Structural Annotation Overuse52 hits · 94 pts
SeverityFileLineSnippetContext
LOWinternal/relationships/validation.go61// NOTE: This method *cannot* be used for relationships that will be deleted.COMMENT
LOWpkg/schemadsl/compiler/translator.go313// NOTE: This function behaves differently based on an errorOnMissingReference flag.COMMENT
LOW⚡pkg/schema/v2/clone_test.go628 // Step 1: Compile the schemaCOMMENT
LOW⚡pkg/schema/v2/clone_test.go635 // Step 2: Convert to *SchemaCOMMENT
LOW⚡pkg/schema/v2/clone_test.go640 // Step 3: Resolve the schemaCOMMENT
LOW⚡pkg/schema/v2/clone_test.go645 // Step 4: Clone the resolved schemaCOMMENT
LOW⚡pkg/schema/v2/resolved_test.go646 // Step 1: Compile the schemaCOMMENT
LOW⚡pkg/schema/v2/resolved_test.go653 // Step 2: Convert to *SchemaCOMMENT
LOW⚡pkg/schema/v2/resolved_test.go658 // Step 3: Resolve the schemaCOMMENT
LOW⚡pkg/schema/v2/resolved_test.go686 // Step 1: Compile the schemaCOMMENT
LOW⚡pkg/schema/v2/resolved_test.go693 // Step 2: Convert to *SchemaCOMMENT
LOW⚡pkg/schema/v2/resolved_test.go698 // Step 3: Resolve the schemaCOMMENT
LOW⚡pkg/schema/v2/resolved_test.go703 // Step 4: Convert back to namespace definitionCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go325 // Step 1: Compile the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go332 // Step 2: Convert to *SchemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go337 // Step 3: Resolve the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go342 // Step 4: Flatten the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go347 // Step 5: Convert back to corev1COMMENT
LOW⚡pkg/schema/v2/flatten_test.go352 // Step 6: Generate schema stringCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go668 // Step 1: Compile the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go675 // Step 2: Convert to *SchemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go680 // Step 3: Resolve the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go685 // Step 4: Flatten the schema with FlattenArrows enabledCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go694 // Step 5: Convert back to corev1COMMENT
LOW⚡pkg/schema/v2/flatten_test.go699 // Step 6: Generate schema stringCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1110 // Step 1: Compile the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1117 // Step 2: Convert to *SchemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1122 // Step 3: Resolve the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1127 // Step 4: Flatten the schema with specified optionsCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1136 // Step 5: Convert back to corev1COMMENT
LOW⚡pkg/schema/v2/flatten_test.go1141 // Step 6: Generate schema stringCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1473 // Step 1: Compile the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1480 // Step 2: Convert to *SchemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1485 // Step 3: Resolve the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1490 // Step 4: Flatten the schema with specified optionsCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1565 // Step 1: Compile the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1572 // Step 2: Convert to *SchemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1577 // Step 3: Resolve the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1582 // Step 4: Flatten the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1587 // Step 5: Verify all ResolvedRelationReferences point to valid permissionsCOMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go366 // Step 1: Compile original schemaCOMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go373 // Step 2: Convert to v2 schemaCOMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go377 // Step 3: Convert back to v1COMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go381 // Step 4: Create a type system from the converted definitionsCOMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go389 // Step 5: Run tester functions for each definitionCOMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go601 // Step 1: Compile original schemaCOMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go608 // Step 2: Convert to v2 schemaCOMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go612 // Step 3: Resolve the schemaCOMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go616 // Step 4: Flatten the schemaCOMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go620 // Step 5: Convert flattened schema back to v1COMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go624 // Step 6: Create a type system from the converted flattened definitionsCOMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go632 // Step 7: Run tester functions for each definitionCOMMENT
Verbosity Indicators52 hits · 94 pts
SeverityFileLineSnippetContext
LOWinternal/services/v1/relationships.go588 // If a limit was specified but partial deletion is not allowed, we need to check if theCOMMENT
LOWinternal/services/v1/watch.go200 // If there are filters, we need to check if the update matches any of them.COMMENT
LOW⚡pkg/schema/v2/clone_test.go628 // Step 1: Compile the schemaCOMMENT
LOW⚡pkg/schema/v2/clone_test.go635 // Step 2: Convert to *SchemaCOMMENT
LOW⚡pkg/schema/v2/clone_test.go640 // Step 3: Resolve the schemaCOMMENT
LOW⚡pkg/schema/v2/clone_test.go645 // Step 4: Clone the resolved schemaCOMMENT
LOW⚡pkg/schema/v2/resolved_test.go646 // Step 1: Compile the schemaCOMMENT
LOW⚡pkg/schema/v2/resolved_test.go653 // Step 2: Convert to *SchemaCOMMENT
LOW⚡pkg/schema/v2/resolved_test.go658 // Step 3: Resolve the schemaCOMMENT
LOW⚡pkg/schema/v2/resolved_test.go686 // Step 1: Compile the schemaCOMMENT
LOW⚡pkg/schema/v2/resolved_test.go693 // Step 2: Convert to *SchemaCOMMENT
LOW⚡pkg/schema/v2/resolved_test.go698 // Step 3: Resolve the schemaCOMMENT
LOW⚡pkg/schema/v2/resolved_test.go703 // Step 4: Convert back to namespace definitionCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go325 // Step 1: Compile the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go332 // Step 2: Convert to *SchemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go337 // Step 3: Resolve the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go342 // Step 4: Flatten the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go347 // Step 5: Convert back to corev1COMMENT
LOW⚡pkg/schema/v2/flatten_test.go352 // Step 6: Generate schema stringCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go668 // Step 1: Compile the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go675 // Step 2: Convert to *SchemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go680 // Step 3: Resolve the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go685 // Step 4: Flatten the schema with FlattenArrows enabledCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go694 // Step 5: Convert back to corev1COMMENT
LOW⚡pkg/schema/v2/flatten_test.go699 // Step 6: Generate schema stringCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1110 // Step 1: Compile the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1117 // Step 2: Convert to *SchemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1122 // Step 3: Resolve the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1127 // Step 4: Flatten the schema with specified optionsCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1136 // Step 5: Convert back to corev1COMMENT
LOW⚡pkg/schema/v2/flatten_test.go1141 // Step 6: Generate schema stringCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1473 // Step 1: Compile the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1480 // Step 2: Convert to *SchemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1485 // Step 3: Resolve the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1490 // Step 4: Flatten the schema with specified optionsCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1565 // Step 1: Compile the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1572 // Step 2: Convert to *SchemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1577 // Step 3: Resolve the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1582 // Step 4: Flatten the schemaCOMMENT
LOW⚡pkg/schema/v2/flatten_test.go1587 // Step 5: Verify all ResolvedRelationReferences point to valid permissionsCOMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go366 // Step 1: Compile original schemaCOMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go373 // Step 2: Convert to v2 schemaCOMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go377 // Step 3: Convert back to v1COMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go381 // Step 4: Create a type system from the converted definitionsCOMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go389 // Step 5: Run tester functions for each definitionCOMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go601 // Step 1: Compile original schemaCOMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go608 // Step 2: Convert to v2 schemaCOMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go612 // Step 3: Resolve the schemaCOMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go616 // Step 4: Flatten the schemaCOMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go620 // Step 5: Convert flattened schema back to v1COMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go624 // Step 6: Create a type system from the converted flattened definitionsCOMMENT
LOW⚡pkg/schema/v2/todefinitions_typesystem_test.go632 // Step 7: Run tester functions for each definitionCOMMENT
Hyper-Verbose Identifiers14 hits · 17 pts
SeverityFileLineSnippetContext
LOWinternal/checkbaseline/report/test_report.py6def test_bands_are_sample_quartiles():CODE
LOWinternal/checkbaseline/report/test_report.py14def test_script_data_escapes_html():CODE
LOWinternal/checkbaseline/report/test_history.py80def test_archive_is_immutable_and_checksums_detect_tampering(tmp_path):CODE
LOWinternal/checkbaseline/report/test_history.py94def test_comparison_identity_covers_input_request_policy_and_machine():CODE
LOWinternal/checkbaseline/report/test_history.py118def test_merge_rejects_duplicate_cases_and_conflicting_source():CODE
LOWinternal/checkbaseline/report/test_history.py130def test_invalid_or_partial_measurements_cannot_publish(change):CODE
LOW⚡internal/checkbaseline/report/test_history.py141def test_unknown_cpu_or_runtime_settings_withhold_comparison_keys(field):CODE
LOW⚡internal/checkbaseline/report/test_history.py147def test_exclusive_run_lock_rejects_second_owner(tmp_path):CODE
LOW⚡internal/checkbaseline/report/test_history.py157def test_interrupted_log_is_not_overwritten(tmp_path):CODE
LOW⚡internal/checkbaseline/report/test_history.py165def test_concurrent_index_rebuilds_are_serialized(tmp_path):CODE
LOW⚡internal/checkbaseline/report/test_history.py174def test_incomplete_postgres_configuration_cannot_publish_or_compare(settings):CODE
LOW⚡internal/checkbaseline/report/test_history.py182def test_schema_loads_are_separate_and_unrecorded_history_is_unknown():CODE
LOWinternal/checkbaseline/report/test_history.py193def test_sql_metadata_and_combined_chart_preserve_size_dimensions(tmp_path):CODE
LOWinternal/checkbaseline/report/test_history.py245def test_run_ids_cannot_escape_history_directory(tmp_path):CODE
Example Usage Blocks3 hits · 4 pts
SeverityFileLineSnippetContext
LOWinternal/graph/limits.go37// Example usage:COMMENT
LOWpkg/schema/v2/builder.go27// Example usage:COMMENT
LOWpkg/schema/v2/schema.go28// Example usage:COMMENT
TODO Padding2 hits · 3 pts
SeverityFileLineSnippetContext
LOWinternal/dispatch/graph/graph.go600 // TODO: implement caching for LookupResources resultsCOMMENT
LOWinternal/dispatch/graph/graph.go618 // TODO: implement caching for LookupSubjects resultsCOMMENT
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMinternal/datastore/crdb/ttl_changefeed.go35// origin marker, so suppression at the source is the only robust mechanism.COMMENT
Deep Nesting2 hits · 2 pts
SeverityFileLineSnippetContext
LOWinternal/checkbaseline/report/history.py143CODE
LOWinternal/checkbaseline/report/history.py244CODE