Home / Orama-Interactive / Pixelorama
AI Slop Code RIsk Monitor

Orama-Interactive/Pixelorama

Unleash your creativity with Pixelorama, a powerful and accessible open-source pixel art multitool. Whether you want to create sprites, tiles, animations, or just express yourself in the language of pixel art, this software will realize your pixel-perfect dreams with a vast toolbox of features. Available on Windows, Linux, macOS and the Web!

4.9 Low pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for Orama-Interactive/Pixelorama, a GDScript project with 10,494 GitHub stars. SynthScan examined 6,569 lines of code across 36 source files, recording 20 pattern matches distributed across 9 syntactic categories. The legacy adjusted pattern signal is 4.9 (Low 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.

4.9
Adjusted Signal
4.9
Raw Pattern Score
100%
Time Factor
2026-10-08
Last Push
10.5K
Stars
GDScript
Language
6.6K
Lines of Code
36
Files
20
Pattern Hits
2026-10-12
Scan Date
0.03
HC Hit Rate

Risk Review · v3

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

Cognitive Ownership Risk 15.1/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

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

Agent Over-Engineering Ratio 10.1/100 · LOW

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

PR Review Velocity Impact 23.4/100 · LOW

Which changes need focused human review? 20 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 1MEDIUM 5LOW 14

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 20 distinct pattern matches across 9 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.

Self-Referential Comments3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUMinstaller/utils/nsi2pot.py71# Create a cache of messageValues : [ [fileName1,lineNumber1], [fileName2,lineNumber2]... ] (The same message could appCOMMENT
MEDIUMinstaller/utils/nsi2pot.py73# Create a cache of messageValues : [ label1, label2 ] (The same message could have multiple NSIS labels)COMMENT
MEDIUMinstaller/utils/po2nsi.py42# Define a dict to convert locale names to language namesCOMMENT
Deep Nesting7 hits · 7 pts
SeverityFileLineSnippetContext
LOWinstaller/utils/polib.py177CODE
LOWinstaller/utils/polib.py455CODE
LOWinstaller/utils/polib.py983CODE
LOWinstaller/utils/polib.py1303CODE
LOWinstaller/utils/polib.py1529CODE
LOWinstaller/utils/polib.py1618CODE
LOWinstaller/utils/polib.py1684CODE
Empty Error Handlers1 hit · 5 pts
SeverityFileLineSnippetContext
HIGHinstaller/utils/polib.py527except KeyError:CODE
Dead Code2 hits · 4 pts
SeverityFileLineSnippetContext
MEDIUMinstaller/utils/polib.py1098CODE
MEDIUMinstaller/utils/polib.py1102CODE
AI Structural Patterns3 hits · 3 pts
SeverityFileLineSnippetContext
LOWinstaller/utils/polib.py342CODE
LOWinstaller/utils/polib.py886CODE
LOWinstaller/utils/polib.py1050CODE
Redundant / Tautological Comments1 hit · 2 pts
SeverityFileLineSnippetContext
LOWMisc/Clickable/build-ubports.sh18 # Check if the most recently downloaded build for this architecture is from the same pipelineCOMMENT
Modern Structural Boilerplate1 hit · 1 pts
SeverityFileLineSnippetContext
LOWinstaller/utils/polib.py36__all__ = ['pofile', 'POFile', 'POEntry', 'mofile', 'MOFile', 'MOEntry',CODE
Excessive Try-Catch Wrapping1 hit · 1 pts
SeverityFileLineSnippetContext
LOWinstaller/utils/polib.py1493 except Exception:CODE
Over-Commented Block1 hit · 1 pts
SeverityFileLineSnippetContext
LOWinstaller/utils/polib.py1261 self.current_token = NoneCOMMENT