Exposed Visualization

C+ 74 completed
Other
monorepo / kotlin · tiny
46
Files
3,570
LOC
0
Frameworks
4
Languages

Pipeline State

completed
Run ID
#1530268
Phase
done
Progress
0%
Started
2026-04-16 14:41:52
Finished
2026-04-16 14:41:52
LLM tokens
0
Previous runs
Open data · scored by Repobility · https://repobility.com
#StatusPhaseStartedFinished
Repobility · code-quality intelligence · https://repobility.com
#1530265completed2026-04-16 14:41:522026-04-16 14:41:52

Pipeline Metadata

Stage
Cataloged
Decision
proceed
Novelty
49.41
Framework unique
Isolation
Last stage change
2026-05-10 03:34:40
Deduplication group #51350
Member of a group with 7 similar repo(s) — canonical #1595863 view group →
About: code-quality intelligence by Repobility · https://repobility.com

AI Prompt

Create a Kotlin monorepo structure for an exposed visualization tool. I need to set up the core components, including modules for reflection, the core logic, and specific plugins for IntelliJ and Maven integration. Please structure the project using Gradle, ensuring that the necessary build files (like `pom.xml` and `exposed-er-gradle-plugin`) are in place to manage these interconnected parts. The project should primarily use Kotlin but also accommodate XML and HTML for potential visualization assets.
kotlin monorepo visualization gradle intellij maven exposed android
Generated by gemma4:latest

Catalog Information

Create a Kotlin monorepo structure for an exposed visualization tool. I need to set up the core components, including modules for reflection, the core logic, and specific plugins for IntelliJ and Maven integration. Please structure the project using Gradle, ensuring that the necessary build files (like pom.xml and exposed-er-gradle-plugin) are in place to manage these interconnected parts. The project should primarily use Kotlin but also accommodate XML and HTML for potential visualization a

Tags

kotlin monorepo visualization gradle intellij maven exposed android

Quality Score

C+
74.1/100
Structure
66
Code Quality
100
Documentation
33
Testing
70
Practices
75
Security
92
Dependencies
75

Strengths

  • Good test coverage (65% test-to-source ratio)
  • Consistent naming conventions (PascalCase)
  • Good security practices — no major issues detected
  • Properly licensed project

Weaknesses

  • No CI/CD configuration — manual testing and deployment

Recommendations

  • Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
  • Add a linter configuration to enforce code style consistency

Languages

kotlin
76.6%
xml
12.9%
html
7.0%
markdown
3.5%

Frameworks

None detected

Symbols

property860
method220
class96
function24
enum8

Quality Timeline

2 quality scores recorded.

View File Metrics

Embed Badge

Add to your README:

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