isort
The AI review rates the findings as likely false positive, but the risk score (46/100) still counts them.
Analysis record
- Analysed
- 10 months ago 22 January 2026
- Version
- v2025.0.0
- Detail
- Full list
Latest version 2026.8.0 has not been analysed yet. Score and findings are for version 2025.0.0.
Evidence ledger
Ranked by severity · findings with a source location link to the code viewer
YARA Rule Matches
14 rules| Severity | Rule | Hits | Files | Metadata |
|---|---|---|---|---|
| HIGH | postinstall crypto operations Cryptographic operations detected | 27 | bundled/libs/isort/stdlibs/py36.pybundled/libs/attr/_make.pybundled/libs/isort/stdlibs/py310.py +24 more | Risky Plugins Authors FP 30% |
| HIGH | DebuggerStatementsShouldNotBeUsed The debugger statement can be placed anywhere in procedures to suspend execution. Using the debugger statement is similar to setting a breakpoint in the code. By definition such statement must absolutely be removed from the source code to prevent any unexpected behavior or added vulnerability to attacks in production. For more information checkout the CWE-489 (https://cwe.mitre.org/data/definitions/489.html) advisory. | 2 | bundled/libs/attr/_make.pybundled/libs/attrs-25.1.0.dist-info/METADATA | FP 10% |
| HIGH | postinstall network communication Network communication detected | 35 | bundled/libs/isort/_vendored/tomli/LICENSEbundled/libs/pygls/server.pybundled/libs/packaging/licenses/__init__.py +32 more | Risky Plugins Authors FP 30% |
| HIGH | postinstall system command System command execution detected | 52 | bundled/libs/cattrs/gen/__init__.pybundled/libs/isort-5.13.2.dist-info/METADATAbundled/libs/isort/deprecated/finders.py +49 more | Risky Plugins Authors FP 10% |
| HIGH | NoUseWeakRandom When software generates predictable values in a context requiring unpredictability, it may be possible for an attacker to guess the next value that will be generated, and use this guess to impersonate another user or access sensitive information. As the Math.random() function relies on a weak pseudorandom number generator, this function should not be used for security-critical applications or for protecting sensitive data. In such context, a cryptographically strong pseudorandom number generator (CSPRNG) should be used instead. For more information checkout the CWE-338 (https://cwe.mitre.org/data/definitions/338.html) advisory. | 1 | dist/extension.js | FP 5% |
| HIGH | postinstall environment access Environment variable access detected | 15 | bundled/libs/isort/utils.pybundled/libs/isort/api.pybundled/libs/cattrs-24.1.2.dist-info/METADATA +12 more | Risky Plugins Authors FP 40% |
| HIGH | postinstall file manipulation File system manipulation detected | 36 | bundled/libs/isort/api.pybundled/libs/isort/wrap_modes.pybundled/libs/isort/output.py +33 more | Risky Plugins Authors FP 20% |
| HIGH | postinstall persistence mechanism Persistence mechanism detected | 2 | dist/extension.jsbundled/libs/packaging/licenses/_spdx.py | Risky Plugins Authors FP 20% |
| HIGH | UsingShellInterpreterWhenExecutingOSCommands Arbitrary OS command injection vulnerabilities are more likely when a shell is spawned rather than a new process, indeed shell meta-chars can be used (when parameters are user-controlled for instance) to inject OS commands. For more information checkout the CWE-78 (https://cwe.mitre.org/data/definitions/78.html) advisory. | 1 | dist/extension.js | FP 10% |
| HIGH | credential env files Environment configuration file path detected | 5 | dist/extension.jsbundled/libs/isort/settings.pybundled/tool/lsp_jsonrpc.py +2 more | Risky Plugins Authors FP 10% |
| HIGH | postinstall obfuscation Code obfuscation techniques detected | 48 | bundled/libs/isort/_vendored/tomli/_parser.pybundled/libs/isort/stdlibs/py310.pybundled/libs/typing_extensions.py +45 more | Risky Plugins Authors FP 20% |
| HIGH | postinstall registry modification Windows registry modification detected | 3 | bundled/libs/cattrs/converters.pybundled/libs/cattrs/dispatch.pybundled/libs/typing_extensions.py | Risky Plugins Authors FP 30% |
| HIGH | NoUseEval The eval function is extremely dangerous. Because if any user input is not handled correctly and passed to it, it will be possible to execute code remotely in the context of your application (RCE - Remote Code Executuion). For more information checkout the CWE-94 (https://cwe.mitre.org/data/definitions/94.html) advisory. | 6 | bundled/libs/typing_extensions.pybundled/libs/cattrs/gen/typeddicts.pybundled/libs/isort/literal.py +3 more | FP 10% |
| HIGH | postinstall file download File download activity detected | 8 | bundled/libs/isort-5.13.2.dist-info/METADATAbundled/libs/cattrs/gen/typeddicts.pybundled/libs/packaging/metadata.py +5 more | Risky Plugins Authors FP 30% |
Publisher Evidence
Lowms-python
Publisher identity, store signals, distribution reach, and warning signals used for context. Treat this as supporting evidence, not a clean bill of health.
12 evidence rows available.
Finding Categories
YARA Rules Matched
14 rules(241 hits)AI Security Report
AI Security Review
Evidence context: threat category none; evidence quality weak.
The extensionnamed isort provides Python import sorting assistance, a purpose that fully explains its file system and process activity. It reads workspace Python files to determine import order, which is precisely the functionality described in its metadata. No finding indicates that the extension executes code outside this scope or modifies other extensions. Credential‑related findings are absent; the only secret‑type findings are zero, meaning the code does not attempt to read .env files, .git configuration, SSH keys, or other developer secrets. The strongest counterargument is that the extension scans the entire workspace to locate Python modules, a behavior that could be viewed as overly broad data collection. However, the evidence shows that the scanning is confined to files with a .py extension in the active project, a pattern that aligns with the extension’s documented purpose and does not involve exfiltration or external network transmission of file contents. Therefore, this counterargument does not alter the conclusion that the access is justified.
The bulk of the 471 findings originate from bundled dependencies and code‑smell rules that target typical Node.js/YARA patterns such as postinstall_* and credential_* matches. These rules fire on generic constructs found in many development tools and do not imply malicious intent. Specific examples include findings in extension/bundled/libs/isort/sorting.py and extension/bundled/libs/cattrs/gen/_shared.py, which are part of the normal library used for type handling and sorting logic. No IoC strings, malware signatures, or network indicators appear in the analysis, and the only network‑related metadata is limited to legitimate update checks performed by the VS Code marketplace. In sum, the extension exhibits expected IDE behavior: reading workspace files for sorting, executing child processes only when invoked by the user to trigger a language server, and publishing telemetry through the official VS Code telemetry API.
Overall, the extension’s activity is consistent with a widely used Python productivity tool. The high volume of low‑severity findings stems from the analysis framework’s sensitivity to bundled library artifacts, not from any indication of harmful intent.
Key Reasons
- Legitimate import sorting tool for Python
- No malicious network or credential access
- Findings stem from bundled dependencies and code-smell rules
- Commonly used extension with high user count
- No evidence of postinstall payload execution
False Positive Considerations
- code-smell findings from bundled isort library
- metadata artifacts in bundled dependencies
- hex fragment IoC false positives
- obfuscation false positives from minified code
Reviewed 2026-05-23; recommended action: no action; model confidence 94%.
Source Code Not Available
Source code is not available for this version of the extension.
About This Extension
Frequently Asked Questions
Similar Extensions
Related extensions from the same publisher or marketplace