Scan report

shopsys / shopsys

Vulnerability Critical

Could an attacker exploit mistakes in this code?

485 risk score

Strong warning signs. Do not run or install this without a careful review.

High
19
Medium
229
Low
0

Sources: Bandit, Semgrep, pip-audit

Malicious pattern Low

Does this code look like it is trying to cause harm?

3 risk score

Minor issues. Worth a glance, unlikely to be urgent.

High
1
Medium
0
Low
12

Sources: YARA, ClamAV, GuardDog, dependency checker

Findings overview
261 total findings
Likely real
214
Uncertain
29
Likely noise
18

The risk classifier rates every finding for how likely it is to be a real issue. Likely noise still counts, just much less.

What we found, in plain English

This repository has a critical vulnerability score of 485.0, which means there are serious insecure coding patterns that an attacker could exploit to break into your system. While the code does not appear to be intentionally malicious, it contains many instances of unsafe commands like child_process and shell execution that could lead to command injection attacks if used incorrectly. You should avoid using these dangerous functions unless you have a very specific reason and implement strict input validation to prevent them from being abused. Additionally, there are several medium-priority issues related to Regular Expression Denial-of-Service (ReDoS) risks in your codebase that could slow down or crash applications if exploited. Overall, the repository is not safe for production use without a thorough security review and refactoring of these specific patterns before deployment.

Written by a local language model from the findings below. The risk scores come from the classifier, not from this summary.

Detections by engine

  • Semgrep 248

    Pattern-based code analysis · Vulnerability

  • YARA 8

    Malware signature rules · Malicious pattern

  • GuardDog 3

    Supply-chain attack heuristics · Malicious pattern

  • Dependency checker 2

    CVEs, typosquats and risky installs · Supply chain

Score over time

Overall score each time this repository was scanned.

Findings

Highest severity first. Select a finding to see the code and what it means.

Large result: showing the top 213 of 261 findings (up to 200 per engine, most severe and most likely real first). Totals above include everything.