Drawing Detector

F 31 completed
Other
web_app / javascript · small
101
Files
42,596
LOC
4
Frameworks
9
Languages

Pipeline State

completed
Run ID
#394934
Phase
done
Progress
1%
Started
Finished
2026-04-13 01:31:02
LLM tokens
0

Pipeline Metadata

Stage
Cataloged
Decision
proceed
Novelty
70.53
Framework unique
Isolation
Last stage change
2026-05-10 03:35:17
Deduplication group #57178
Member of a group with 2 similar repo(s) — this repo is canonical view group →
Top concepts (1)
Web Frontend
Provenance: Repobility (https://repobility.com) — every score reproducible from /scan/

AI Prompt

Create a web application for drawing detection. I need the frontend built with React and styled using Tailwind CSS, and I'd like the backend to be implemented using FastAPI. The project structure should accommodate deployment, so please include necessary files or placeholders for Firebase setup, like `firebase.json` and Firestore rules. The goal is to build a functional detector that can be run locally.
javascript react fastapi tailwind web-app python firebase drawing-detector
Generated by gemma4:latest

Catalog Information

yisunguk__drawing-detector

Novelty

3/10

Tags

javascript react fastapi tailwind web-app python firebase drawing-detector

Claude Models

claude-opus-4-6

Quality Score

F
31.4/100
Structure
26
Code Quality
36
Documentation
15
Testing
15
Practices
41
Security
65
Dependencies
60

Strengths

  • CI/CD pipeline configured (github_actions)
  • Containerized deployment (Docker)

Weaknesses

  • Missing README file \u2014 critical for project understanding
  • No LICENSE file \u2014 legal ambiguity for contributors
  • No tests found \u2014 high risk of regressions
  • 5 files with critical complexity need refactoring
  • 6 bare except/catch blocks swallowing errors
  • Potential hardcoded secrets in 1 files
  • 5209 duplicate lines detected \u2014 consider DRY refactoring
  • 17 'god files' with >500 LOC need decomposition

Recommendations

  • Add a comprehensive README.md explaining purpose, setup, usage, and architecture
  • Add a test suite \u2014 start with critical path integration tests
  • Add a linter configuration to enforce code style consistency
  • Add a LICENSE file (MIT recommended for open source)
  • Replace bare except/catch blocks with specific exception types
  • Move hardcoded secrets to environment variables or a secrets manager
  • Address 27 TODO/FIXME items \u2014 consider tracking them as issues

Security & Health

26.8h
Tech Debt (B)
A
OWASP (100%)
FAIL
Quality Gate
A
Risk (14)
Repobility — same analyzer, your code, free for public repos · /scan/
Unknown
License
8.1%
Duplication
Full Security Report AI Fix Prompts SARIF SBOM

Languages

javascript
45.2%
python
29.7%
json
23.3%
css
0.6%
typescript
0.4%
text
0.2%
yaml
0.2%
markdown
0.2%
html
0.1%

Frameworks

FastAPI React Tailwind CSS Vite

Concepts (1)

Repobility analysis · methodology at https://repobility.com/research/
CategoryNameDescriptionConfidence
Same scanner, your repo: https://repobility.com — Repobility
auto_categoryWeb Frontendweb-frontend70%

Quality Timeline

1 quality score recorded.

View File Metrics

Embed Badge

Add to your README:

![Quality](https://repos.aljefra.com/badge/119284.svg)
Quality BadgeSecurity Badge
Export Quality CSVDownload SBOMExport Findings CSV