Nextjs Echo Back Blog App

C+ 75 completed
Other
infrastructure / go · small
154
Files
10,365
LOC
0
Frameworks
3
Languages

Pipeline State

completed
Run ID
#1449553
Phase
done
Progress
0%
Started
2026-04-16 09:03:51
Finished
2026-04-16 09:03:51
LLM tokens
0

Pipeline Metadata

Stage
Skipped
Decision
skip_scaffold_dup
Novelty
39.00
Framework unique
Isolation
Last stage change
2026-04-16 18:15:42
Deduplication group #49205
Member of a group with 42 similar repo(s) — canonical #667575 view group →
Source: Repobility analyzer · https://repobility.com

AI Prompt

Create a blog web application backend using Go with the Echo framework. The goal is to read and display Markdown files, such as those from Zenn or Qiita, that are managed in a local Markdown file structure. The backend should be designed to be deployed on Cloud Run and potentially integrated with Supabase. Please structure the code using handlers, services, and models, and include necessary configuration files for deployment.
go echo markdown blog backend next.js cloud-run supabase terraform
Generated by gemma4:latest

Catalog Information

Create a blog web application backend using Go with the Echo framework. The goal is to read and display Markdown files, such as those from Zenn or Qiita, that are managed in a local Markdown file structure. The backend should be designed to be deployed on Cloud Run and potentially integrated with Supabase. Please structure the code using handlers, services, and models, and include necessary configuration files for deployment.

Tags

go echo markdown blog backend next.js cloud-run supabase terraform

Quality Score

C+
75.3/100
Structure
75
Code Quality
89
Documentation
56
Testing
85
Practices
68
Security
65
Dependencies
70

Strengths

  • CI/CD pipeline configured (github_actions)
  • Good test coverage (80% test-to-source ratio)
  • Consistent naming conventions (snake_case)
  • Low average code complexity — well-structured code
  • Containerized deployment (Docker)

Weaknesses

  • No LICENSE file — legal ambiguity for contributors
  • Potential hardcoded secrets in 6 files
  • 981 duplicate lines detected — consider DRY refactoring

Recommendations

  • Add a linter configuration to enforce code style consistency
  • Add a LICENSE file (MIT recommended for open source)
  • Move hardcoded secrets to environment variables or a secrets manager

Languages

go
66.1%
markdown
33.0%
yaml
0.9%

Frameworks

None detected

Symbols

method122
function40
struct32
interface11

Quality Timeline

1 quality score recorded.

View File Metrics

Embed Badge

Add to your README:

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