depends: the two bindings, measured again on the tree facts and not taken

check: dependencies are read when the depends check asks, and where named

figures: the cross-hit row is read from the probes' committed rows

check: the modules a module depends on are read beside it

depends: storedness, merged depends and transitive triggers read from the tree

constrains: a field Odoo cannot trigger on is asked for by its inputs

layers: an advisory finding gates nothing in the answer layers either

depends: a name assigned records, measured and not taken

ondelete: a read through mapped(), measured and not taken

depends: a read straight off a call that keeps the records is a read

eval: the pipeline rows re-measured on the nine Odoo questions

adversarial: the probes' rows are committed, and CI checks them

artifacts: the measurements move out of the repository's root

check: the eval rows re-measured on the subjects left, and checked

layers: a citation written as a list under the label is a claim

fieldtest: a file two checkers could not read is one file

depends: a read through a method's own output, measured and kept exempt

Merge origin/main: the depends sweep (10a, 10b) and 3.72

depends: what a file says a method computes is its output; a lambda stays unread

depends: what a string names and what a subscript picks are reads

readme: the coverage figures nothing was counting

constrains: a dotted name is read, not matched

onchange: the same check made again on the server backs it

onchange: backed by a constraint on its field, refused only when taken back

onchange: a dead _sql_constraints backs nothing on 19

depends: a mapped() path is a read

sudo: a public page reading what it publishes is re-scoped

sudo: a domain on records the caller already holds is re-scoped

rule: _sql_constraints is ignored from Odoo 19

datetime: the rule sees where the value goes

sudo: re-scoping has to re-apply every rule everybody gets

depends-unread: an override that calls super() adds triggers for the chain

narrow: the last three named false-positive classes, and one weakness found on the way

xml: read the data files, and ask noupdate the question per record

recursion: ask whether the ORM already refuses the cycle, and whether it can form one

tests: the grounding cap gets a subject that still overflows it

figures: every present-tense number, checked against the artifact it came from

precision: read the named false positives, and the misses that named themselves

ascii: make the fallback reachable, and the clone survive the gateway

narrow: one corpus, and it is Odoo

evidence: prune by the time in the bundle, not the time on the inode

external: run somebody else's analyser, and put a number on their rules

review: a pass over the tool itself, and the silence it was keeping

readme: the wordmark that actually ships, and a shot of it running

banner: three times the wordmark, and the two hues become a sweep

banner: solid NEXA in two hues, over an amber bar

report: findings in likelihood order, because history has an opinion

triggers: the two conditional rules learn to ask the tree

banner: the framed NX wordmark, in the colours it already had

severity: two axes, and the gate falls out of the second one