Scan report

epicserve / django-base-site

Vulnerability High

Could an attacker exploit mistakes in this code?

160 risk score

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

High
3
Medium
28
Low
64

Sources: Bandit, Semgrep, pip-audit

Malicious pattern Medium

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

32 risk score

Real issues worth reviewing before you rely on this code.

High
3
Medium
19
Low
11

Sources: YARA, ClamAV, GuardDog, dependency checker

Findings overview
128 total findings
Likely real
106
Uncertain
0
Likely noise
22

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 shows two distinct levels of security issues that need immediate attention before it can be used in production. The most critical finding is a high vulnerability risk score of 160, which indicates the code contains dangerous patterns like running command outputs directly into shells and missing CSRF protection, making it highly exploitable by attackers. While there are also medium-level concerns about potential malicious intent, these appear to stem from common insecure coding practices rather than intentional attacks. The developer should prioritize fixing the high-risk issues first, such as securing shell commands and enabling HTML autoescaping, before considering the repository safe for 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 78

    Pattern-based code analysis · Vulnerability

  • Dependency checker 29

    CVEs, typosquats and risky installs · Supply chain

  • Bandit 17

    Python security linter · Vulnerability

  • YARA 3

    Malware signature rules · Malicious pattern

  • GuardDog 1

    Supply-chain attack heuristics · Malicious pattern

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.