Sink boundary: Input is evaluated by a template engine as expressions instead of plain text.
The pack does not provide a callable signature for this record; the watched access path is shown directly.
| Arg | Access path | Purpose | Watched |
|---|---|---|---|
| Argument[0] | Argument[0] | The access path Atropos marks for this model. | ▲ sink |
Attacker's-eye view · template-injection
Template syntax executes in the rendering context and may access data or capabilities.
// modeled boundary: Argument[0]
PageTemplate(attacker_influenced_value);
1Keep user input in data slots, not template source.
2Use a sandbox only as defense in depth.
3Escape for the actual output context.
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 Argument[0] as a template-injection sink. 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 →Same behavior
●templatejavascript●compilejavascript●renderjavascript●compilejavascript●compilejavascript●precompilejavascriptAcross languages
●templatejavascript●compilejavascript●renderjavascript●compilejavascript●compilejavascript●precompilejavascriptWhat neutralizes it
No sanitizer of this kind is modeled.
Model facts · verbatim from the pack
| Role | Kind | Access path | Model ID | Confidence |
|---|---|---|---|---|
| sink | template-injection | Argument[0] | python.chameleon.pagetemplate.a0 | medium · corrob. 1 |