MalDet

Scan report

sinavm / SVM

Report Rescan
Vulnerability High

Could an attacker exploit mistakes in this code?

136 risk score

Serious issues. Review the high-severity findings before using it.

High
16
Medium
6
Low
0

Sources: Bandit, Semgrep, pip-audit

Malicious pattern Safe

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

0 risk score

No issues of this kind were found.

High
0
Medium
0
Low
0

Sources: YARA, ClamAV, GuardDog, dependency checker

Findings overview
22 total findings
Likely real
15
Uncertain
6
Likely noise
1

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 high vulnerability score of 136.0, which means there are several dangerous coding patterns that could let attackers exploit the code if it were used in production. While the malicious-pattern risk is low at 0.0, indicating no obvious signs of intentional harm, the actual security issues found are mostly standard mistakes rather than clever attacks. The most critical issue is that debug logging is turned on, which would leak sensitive information to anyone viewing the site. Another serious problem involves executing commands with user input, a common error where developers forget to sanitize data before running it. Additionally, there is a risk of supply-chain attacks because GitHub Actions steps are using tags or branch names without proper integrity checks. These findings represent ordinary insecure coding practices that should be fixed to make the code safer for real-world use.

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 22

    Pattern-based code analysis · Vulnerability

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.