Big Wylly Style

F 44 completed
Other
monorepo / typescript · small
265
Files
51,819
LOC
2
Frameworks
8
Languages

Pipeline State

completed
Run ID
#1535831
Phase
done
Progress
0%
Started
2026-04-16 16:45:29
Finished
2026-04-16 16:45:29
LLM tokens
0

Pipeline Metadata

Stage
Skipped
Decision
skip_scaffold_dup
Novelty
41.00
Framework unique
Isolation
Last stage change
2026-04-16 18:15:42
Deduplication group #47558
Member of a group with 247 similar repo(s) · framework reactcanonical #1474884 view group →
Open data scored by Repobility · https://repobility.com

AI Prompt

Create a design system boilerplate inspired by shadcn, named 'big-wylly-style'. I need this to be structured as a monorepo using Next.js and TypeScript. The core components should live in a dedicated package, say `@wyllo/ui`. Include a showcase application, perhaps a gallery, built with Next.js. Additionally, I need to incorporate Python scripts for governance, specifically a governance auditor that checks components against defined rules in a JSON file, and a script to regenerate a codebase index.
typescript next.js monorepo design-system react python json ui-library
Generated by gemma4:latest

Catalog Information

Create a design system boilerplate inspired by shadcn, named 'big-wylly-style'. I need this to be structured as a monorepo using Next.js and TypeScript. The core components should live in a dedicated package, say @wyllo/ui. Include a showcase application, perhaps a gallery, built with Next.js. Additionally, I need to incorporate Python scripts for governance, specifically a governance auditor that checks components against defined rules in a JSON file, and a script to regenerate a codebase ind

Tags

typescript next.js monorepo design-system react python json ui-library

Quality Score

F
44.4/100
Structure
47
Code Quality
54
Documentation
37
Testing
15
Practices
48
Security
66
Dependencies
90

Strengths

  • CI/CD pipeline configured (github_actions)
  • Code linting configured (eslint)

Weaknesses

  • No LICENSE file — legal ambiguity for contributors
  • No tests found — high risk of regressions
  • 5 files with critical complexity need refactoring
  • Potential hardcoded secrets in 1 files
  • 5668 duplicate lines detected — consider DRY refactoring
  • 10 'god files' with >500 LOC need decomposition

Recommendations

  • Add a test suite — start with critical path integration tests
  • Add a LICENSE file (MIT recommended for open source)
  • Move hardcoded secrets to environment variables or a secrets manager

Languages

typescript
47.3%
json
43.9%
python
4.2%
markdown
4.1%
css
0.2%
yaml
0.1%
javascript
0.1%
text
0.1%

Frameworks

React Next.js

Symbols

function453
variable398
constant130
method111
type_alias54
interface11
class7
property1

API Endpoints (2)

Same analyzer free for public repos: https://repobility.com
MethodPathHandlerFramework
Repobility (the analyzer behind this table) · https://repobility.com
GET--corner-radiusproperties.getExpress
GET--corner-smoothingproperties.getExpress

Quality Timeline

1 quality score recorded.

View File Metrics
Want this analysis on your repo? https://repobility.com/scan/

Embed Badge

Add to your README:

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