jinja2 3.1.6
- Source
- https://github.com/pallets/jinja
- Artifact scanned
jinja2-3.1.6-py3-none-any.whl- Compared with
jinja2-3.1.5-py3-none-any.whl(0 signals introduced since)- Files
- 27 scanned, 4 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 11 info
- Scan time
- 9.1 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 9 of 9 warn and critical signals; 9 demoted to info.
- Disclude version
- 4.3.0
- Scanned (UTC)
- 2026-10-23 01:03
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
r -
�ׇׁׂׅׄؐ-ًؚ-ٰٟۖ-ۜ۟-۪ۤۧۨ-ܑۭܰ-݊ަ-ް߫-߽߳ࠖ-࠙ࠛ-ࠣࠥ-ࠧࠩ-࡙࠭-࡛࣓-ࣣ࣡-ःऺ-़ा-ॏ॑-ॗॢॣঁ-ঃ়া-ৄেৈো-্ৗৢৣ৾ਁ-ਃ਼ਾ-ੂੇੈੋ-੍ੑੰੱੵઁ-ઃ઼ા-ૅે-ૉો-્ૢૣૺ-૿ଁ-ଃ଼ା-ୄେୈୋ-୍ୖୗୢୣஂா-ூ… -
��ꪾ꪿꫁ꫫ-ꫯꫵ꫶ꯣ-ꯪ꯬꯭ﬞ⟨U+FE00⟩-⟨U+FE0F⟩︠-︯︳︴﹍-﹏_𐇽𐋠𐍶-𐍺𐨁-𐨃𐨅𐨆𐨌-𐨏𐨸-𐨿𐨺𐫦𐫥𐴤-𐽆𐴧-𐽐𑀀-𑀂𑀸-𑁆𑁿-𑂂𑂰-𑂺𑄀-𑄂𑄧-𑄴𑅅𑅆𑅳𑆀-𑆂𑆳-𑇀𑇉-𑇌𑈬-𑈷𑈾𑋟-𑋪𑌀-𑌃𑌻𑌼𑌾-𑍄𑍇𑍈𑍋-𑍍𑍗…likely benign A generated Unicode identifier-character table in Jinja2's identifier module.Reasoning
The line is a long character class of Unicode identifier-continuation ranges, which Jinja2 uses to match valid Python identifiers. The invisible tag and format characters are part of the Unicode ID_Continue tables, not a hidden payload. The raw pass has a high false-positive rate, and nothing here decodes or executes anything.
-
=likely benign Loads cached compiled template bytecode from the bytecode cache.Reasoning
marshal.load reads Jinja2's own bytecode cache files written by the same library. Unmarshalling untrusted cache data is a known risk, but this is the standard, expected use in a legitimate template cache, and the surrounding code only resets on read errors.
-
# Raise an exception at the correct line number. : =likely benign Compiles a stub that raises an exception at a chosen line for traceback rewriting.Reasoning
This builds a padded source string so that a raised exception reports the right line number in a rewritten traceback. The string is internal and contains no external input, which is a standard debugging technique.
-
return . # type: ignorelikely benign Executes generated template code while capturing a traceback.Reasoning
Executes compiled template code in the debug traceback machinery so that the original error can be reproduced and its traceback captured. The code comes from the template compiler, so this is the expected behaviour of Jinja2's debugger.
-
""" return compile(source, filename, "exec") @typing.overloadlikely benign Compiles generated template source into a Python code object.Reasoning
This is Environment.compile, which turns template source into a code object. Compiling template source is the core function of a template engine. The source comes from template files the application chooses to load.
-
= = =likely benign Executes precompiled template code to build a Template object.Reasoning
This is the from_code/from_module_dict path that executes precompiled template code in a namespace. It is the documented mechanism for loading precompiled templates, and the code comes from the template compiler, not from an untrusted network source in this snippet.
-
=likely benign Imports a configured module to load its precompiled templates.Reasoning
ModuleLoader imports a configured package module by name in order to load precompiled templates from it. The module name comes from the application's loader configuration, not from template content, which is the expected pattern for this loader.
-
return returnlikely benign Dynamically imports a module or attribute from a dotted import name.Reasoning
This is the import_string helper, which resolves a dotted name to an object. Dynamic import is its purpose, and the name is supplied by the calling application, as is standard in this utility.
-
return returnlikely benign Resolves an attribute from a dynamically imported module in import_string.Reasoning
This is the same import_string helper, with the getattr fallback for resolving an attribute. It is ordinary library behaviour, and the import path is a caller-provided configuration value.
Reproduce This Scan
Run disclude locally to verify. These commands scan the published file; the "new in this release" marks come from comparing it with the previous release's file, which they don't repeat. Add --format sarif for SARIF output. Add --llm (with an API key in the environment) to include the LLM review.
|