Eventium

B 81 completed
Other
containerized / haskell · small
140
Files
9,630
LOC
0
Frameworks
4
Languages

Pipeline State

completed
Run ID
#1139430
Phase
done
Progress
0%
Started
2026-04-15 15:40:00
Finished
2026-04-15 15:40:00
LLM tokens
0

Pipeline Metadata

Stage
Cataloged
Decision
proceed
Novelty
52.64
Framework unique
Isolation
Last stage change
2026-05-10 03:34:57
Deduplication group #52501
Member of a group with 12 similar repo(s) — canonical #1212964 view group →
Repobility's GitHub App fixes findings like these · https://github.com/apps/repobility-bot

AI Prompt

Create a guide or boilerplate setup for building an event-sourced application using Haskell. I need to see how to integrate the core abstractions, specifically using a pluggable storage backend like PostgreSQL or SQLite. The setup should demonstrate using the `eventium-core` library alongside a specific backend package. Please include examples of defining a projection, implementing a command handler, and running a minimal working example that applies a command.
haskell event-sourcing cqrs eventium postgresql sqlite functional backend
Generated by gemma4:latest

Catalog Information

Create a guide or boilerplate setup for building an event-sourced application using Haskell. I need to see how to integrate the core abstractions, specifically using a pluggable storage backend like PostgreSQL or SQLite. The setup should demonstrate using the eventium-core library alongside a specific backend package. Please include examples of defining a projection, implementing a command handler, and running a minimal working example that applies a command.

Tags

haskell event-sourcing cqrs eventium postgresql sqlite functional backend

Quality Score

B
81.4/100
Structure
76
Code Quality
100
Documentation
65
Testing
75
Practices
74
Security
90
Dependencies
60

Strengths

  • CI/CD pipeline configured (github_actions)
  • Good test coverage (36% test-to-source ratio)
  • Consistent naming conventions (PascalCase)
  • Low average code complexity — well-structured code
  • Good security practices — no major issues detected
  • Containerized deployment (Docker)
  • Properly licensed project

Weaknesses

  • Potential hardcoded secrets in 1 files
  • 306 duplicate lines detected — consider DRY refactoring

Recommendations

  • Add a linter configuration to enforce code style consistency
  • Move hardcoded secrets to environment variables or a secrets manager

Languages

haskell
52.2%
markdown
38.0%
yaml
5.7%
shell
4.1%

Frameworks

None detected

Quality Timeline

1 quality score recorded.

View File Metrics

Embed Badge

Add to your README:

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