1
81%
main: 83%

Ran 08 Jul 2026 12:56AM UTC

Files 32

Run time 1s

Badge

Embed ▾

Committed 08 Jul 2026 12:51AM UTC coverage: 80.661% (+0.5%) from 80.202%

Job # #2375.1

Build Type

Pull #743

github

Committed by

khatchad

Commit Message

Address review: precise callee return-taint; clarify the two failure messages

The return-taint tracking in `scanForTaintedNumpySinks` was dead: the generic def-taint loop ran unconditionally, so a call site was tainted even when every analyzed callee returned clean. Now an analyzed-clean callee set skips the def-taint (precise), while an unanalyzed callee (library summary, no IR) or a tainted return falls through to the conservative path. The code-15 message now cites `Tensor.numpy()` (disambiguating from the new numpy-module precondition) and the code-16 message says "values derived from its parameters" (the condition is transitive flow, not direct application).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01He1ULx8nRoHzGicMryry1A

Pull Request Pull Request #743: Add a safety precondition for numpy applied to parameter-flowing values

Coverage Stats

1927 of 2389 relevant lines covered (80.66%)

0.81 hits per line

ponder-lab / Hybridize-Functions-Refactoring / #2375 / 1
81%
main: 83%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job #2375.1

ponder-lab / Hybridize-Functions-Refactoring / #2375 / 1 81% main: 83%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job #2375.1

ponder-lab / Hybridize-Functions-Refactoring / #2375 / 1
81%
main: 83%

README BADGES
x