Home / Manisso / fsociety
AI Slop Code RIsk Monitor

Manisso/fsociety

fsociety Hacking Tools Pack – A Penetration Testing Framework

12.0 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for Manisso/fsociety, a Python project with 12,331 GitHub stars. SynthScan examined 2,760 lines of code across 14 source files, recording 15 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 12.0 (Moderate pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

12.0
Adjusted Signal
12.0
Raw Pattern Score
100%
Time Factor
2026-07-21
Last Push
12.3K
Stars
Python
Language
2.8K
Lines of Code
14
Files
15
Pattern Hits
2026-10-12
Scan Date
0.57
HC Hit Rate

Risk Review · v3

Use each vector to guide manual verification of the underlying findings.

Cognitive Ownership Risk 5.3/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 3 finding(s).

Hallucinated Dependency & Supply Chain Risk 36.4/100 · MEDIUM

Are imports declared and package/API names verified? 8 finding(s).

Agent Over-Engineering Ratio 11.9/100 · LOW

Are wrappers, guards, and repeated structures necessary? 6 finding(s).

PR Review Velocity Impact 64.4/100 · HIGH

Which changes need focused human review? 15 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 8MEDIUM 1LOW 6

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 15 distinct pattern matches across 4 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Cross-Language Confusion8 hits · 25 pts
SeverityFileLineSnippetContext
HIGHfsociety.py223 os.system("cd fsociety && bash ./update.sh")STRING
HIGHfsociety.py463 os.system("cd %s && ./configure && make && make install" %STRING
HIGHfsociety.py522 os.system("cd %s && python setup.py install" % self.installDir)STRING
HIGHfsociety.py999 os.system("cd %s && chmod +x install.sh && ./install.sh" % self.installDir)STRING
HIGHfsociety.py1024 "gem install bundler && bundle install --without prof && rake install")STRING
HIGHfsociety.py1038 "git clone --depth=1 https://github.com/samyoyo/weeman.git && cd weeman && python weeman.py")STRING
HIGHfsociety.py1082 "git clone --depth=1 https://github.com/AlisamTechnology/ATSCAN.git && cd ATSCAN && perl atscan.pl")CODE
HIGHfsociety.py1319 "cd AndroidPINCrack && python AndroidPINCrack.py -H %s -s %s" % (key, salt))CODE
Excessive Try-Catch Wrapping4 hits · 5 pts
SeverityFileLineSnippetContext
LOWfsociety.py1157 except Exception as message:CODE
LOWfsociety.py1761 except Exception as ex:CODE
LOWfsociety.py1811 except Exception as ex:CODE
MEDIUMfsociety.py739def run(self):CODE
Hyper-Verbose Identifiers2 hits · 2 pts
SeverityFileLineSnippetContext
LOWfsociety.py1995def check_wpstorethemeremotefileupload(sites):CODE
LOWfsociety.py2007def check_wpcontactcreativeform(sites):CODE
Over-Commented Block1 hit · 1 pts
SeverityFileLineSnippetContext
LOWfsociety.py1#!/usr/bin/env python2COMMENT