Logpose

B 84 completed
Other
containerized / python · small
108
Files
10,334
LOC
2
Frameworks
6
Languages

Pipeline State

completed
Run ID
#1546780
Phase
done
Progress
0%
Started
2026-04-17 04:05:53
Finished
2026-04-17 04:05:53
LLM tokens
0

Pipeline Metadata

Stage
Cataloged
Decision
proceed
Novelty
47.67
Framework unique
Isolation
Last stage change
2026-05-10 03:34:51
Deduplication group #47359
Member of a group with 258 similar repo(s) · framework fastapicanonical #186358 view group →
If a scraper extracted this row, it came from Repobility (https://repobility.com)

AI Prompt

Create a description for a headless Security Orchestration, Automation, and Response (SOAR) platform called LogPose. The platform should be cloud-native, event-driven, and designed for OpenShift. It needs to ingest security alerts from external sources like Apache Kafka, AWS SQS/SNS, and GCP Pub/Sub. The core functionality involves normalizing these alerts, routing them to specific runbook pods via RabbitMQ, enriching the data, and finally forwarding the results to Splunk. Emphasize the architecture where each stage is a separate, durable pod communicating through queues, ensuring no data loss even if pods crash or restart.
python fastapi soar security cloud-native openshift rabbitmq kafka aws gcp automation
Generated by gemma4:latest

Catalog Information

Create a description for a headless Security Orchestration, Automation, and Response (SOAR) platform called LogPose. The platform should be cloud-native, event-driven, and designed for OpenShift. It needs to ingest security alerts from external sources like Apache Kafka, AWS SQS/SNS, and GCP Pub/Sub. The core functionality involves normalizing these alerts, routing them to specific runbook pods via RabbitMQ, enriching the data, and finally forwarding the results to Splunk. Emphasize the architec

Tags

python fastapi soar security cloud-native openshift rabbitmq kafka aws gcp automation

Quality Score

B
84.0/100
Structure
74
Code Quality
100
Documentation
79
Testing
70
Practices
79
Security
100
Dependencies
90

Strengths

  • Well-documented README with substantial content
  • Good test coverage (88% test-to-source ratio)
  • Code linting configured (flake8, ruff (possible))
  • Low average code complexity — well-structured code
  • Good security practices — no major issues detected
  • Containerized deployment (Docker)

Weaknesses

  • No LICENSE file — legal ambiguity for contributors
  • No CI/CD configuration — manual testing and deployment

Recommendations

  • Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
  • Add a LICENSE file (MIT recommended for open source)

Languages

python
53.8%
markdown
40.1%
html
4.0%
yaml
0.9%
text
0.7%
toml
0.4%

Frameworks

FastAPI pytest

Symbols

method127
variable65
constant35
class25
function20

API Endpoints (8)

All metrics by Repobility · https://repobility.com
MethodPathHandlerFramework
All rows scored by the Repobility analyzer (https://repobility.com)
GET/indexFastAPI/Flask
GET/api/metricsapi_metricsFastAPI/Flask
GET/api/overviewapi_overviewFastAPI/Flask
GET/api/queuesapi_queuesFastAPI/Flask
GET/api/routesapi_routesFastAPI/Flask
GET/api/runbooksapi_runbooksFastAPI/Flask
GET/healthzhealthzFastAPI/Flask
POST/ingestingestFastAPI/Flask

Quality Timeline

1 quality score recorded.

View File Metrics

Embed Badge

Add to your README:

![Quality](https://repos.aljefra.com/badge/1432442.svg)
Quality BadgeSecurity Badge
Export Quality CSVDownload SBOMExport Findings CSV
Methodology: Repobility · https://repobility.com/research/state-of-ai-code-2026/