Summary boundary: A transformation changes representation while carrying the original trust relationship forward.
The pack does not provide a callable signature for this record; the watched access path is shown directly.
No positional argument is specified; inspect the return value or named access path in the model facts below.
No CWE mapping in this fact
The model classifies the behavior as transform; no CWE relationship is attached to this record.
Attacker's-eye view · transform
Validation is assumed after conversion even though the transformed value still encodes attacker control.
// modeled boundary: Receiver -> ReturnValue
toSorted(attacker_influenced_value);
1Identify what guarantees the transform provides.
2Revalidate after decoding or conversion.
3Trace the transformed value to its next boundary.
These checks require the surrounding codebase. The model names the boundary; it does not decide reachability or prove that a guard dominates every path.
Is this a bug in your code?Atropos stops here — by design
Atropos identifies Receiver -> ReturnValue as a transform summary. It cannot see whether untrusted data reaches this call in your repository.
Lachesis is the codebase-level step: it traces reachability and guards for this symbol.
Check this symbol in Lachesis →Across languages
No cross-language match.
What neutralizes it
No sanitizer of this kind is modeled.
Model facts · verbatim from the pack
| Role | Kind | Access path | Model ID | Confidence |
|---|---|---|---|---|
| summary | transform | Receiver -> ReturnValue | javascript.array.tosorted.recv-ret | high · corrob. 2 |