Mdviewer

D 54 completed
Other
unknown / swift · tiny
36
Files
4,423
LOC
0
Frameworks
6
Languages

Pipeline State

completed
Run ID
#1542371
Phase
done
Progress
0%
Started
2026-04-16 21:23:08
Finished
2026-04-16 21:23:08
LLM tokens
0

Pipeline Metadata

Stage
Cataloged
Decision
proceed
Novelty
29.68
Framework unique
Isolation
Last stage change
2026-05-10 03:34:51
Deduplication group #47380
Member of a group with 1,432 similar repo(s) — canonical #1436887 view group →
Powered by Repobility — scan your code at https://repobility.com

AI Prompt

Create a native macOS Markdown viewer and editor application using SwiftUI and AppKit. The core features must include seamless, bidirectional synchronization between the editor and a live preview, anchored precisely by headings. The application needs to support multiple view modes: a dedicated editor view, a split-pane view, and a full-screen preview with a sidebar outline (H1-H6). Crucially, all styling—including editor fonts, colors, and the full CSS for all Markdown elements—must be controllable via a single, editable `styles.json` file, allowing for hot-reloading of styles without restarting. Additionally, implement robust file handling, including opening files via Finder drag-and-drop, automatic refreshing when files change externally, and export functionality to both PDF and self-contained HTML.
swift macos swiftui appkit markdown editor viewer native-app ui-design json-config
Generated by gemma4:latest

Catalog Information

Create a native macOS Markdown viewer and editor application using SwiftUI and AppKit. The core features must include seamless, bidirectional synchronization between the editor and a live preview, anchored precisely by headings. The application needs to support multiple view modes: a dedicated editor view, a split-pane view, and a full-screen preview with a sidebar outline (H1-H6). Crucially, all styling—including editor fonts, colors, and the full CSS for all Markdown elements—must be controlla

Tags

swift macos swiftui appkit markdown editor viewer native-app ui-design json-config

Quality Score

D
54.1/100
Structure
48
Code Quality
47
Documentation
73
Testing
0
Practices
77
Security
100
Dependencies
80

Strengths

  • Consistent naming conventions (PascalCase)
  • Good security practices — no major issues detected

Weaknesses

  • No LICENSE file — legal ambiguity for contributors
  • No tests found — high risk of regressions
  • No CI/CD configuration — manual testing and deployment
  • 1 files with critical complexity need refactoring
  • 369 duplicate lines detected — consider DRY refactoring
  • 2 'god files' with >500 LOC need decomposition

Recommendations

  • Add a test suite — start with critical path integration tests
  • Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
  • Add a linter configuration to enforce code style consistency
  • Add a LICENSE file (MIT recommended for open source)

Languages

swift
77.2%
markdown
13.2%
html
5.9%
javascript
1.7%
yaml
1.6%
json
0.5%

Frameworks

None detected

Symbols

property508
method92
struct52
class9
extension5
function1
enum1
variable1

Quality Timeline

1 quality score recorded.

View File Metrics

Embed Badge

Add to your README:

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