microservices-architect

Fail

Audited by Runlayer on Mar 7, 2026

Risk Level: HIGH
Scan Summary
Max Score
93%
Files
6
Flagged
4
Chunks
12
Flagged Files (4)
microservices-architect/references/observability.mdHIGH
92.8%

Tool passed security scan

Malicious tool definition detected

Remediate: - Rollback order-service - Verify errors stopped - Create ticket for bug fix ``` ## Summary Observability is non-negotiable in microservices: **Must-Haves:** - Structured logging with correlation IDs - Metrics (RED/USE methodology) - Distributed tracing (OpenTelemetry) - Centralized log aggregation - SLO tracking with error budgets - Actionable alerts with runbooks **Best Practices:** - Correlate metrics, logs, and traces - Define SLOs based on user experience - Alert on symptoms, not

microservices-architect/references/patterns.mdLOW
73.5%

Tool passed security scan

Malicious tool definition detected

Tool: microservices-architect/references/patterns.md [2/2] Description: saga_id UUID PRIMARY KEY, saga_type VARCHAR(50), current_step VARCHAR(50), status VARCHAR(20), payload JSONB, created_at TIMESTAMP, updated_at TIMESTAMP ); On orchestrator restart: - Load incomplete sagas - Resume from last completed step - Execute remaining steps or compensations ``` ### Event Sourcing **Purpose:** Store all state changes as events, derive current state by replaying.

microservices-architect/references/data.mdLOW
70.0%

Tool passed security scan

Malicious tool definition detected

microservices-architect/references/decomposition.mdLOW
61.8%

Tool passed security scan

Passed Files (2)Click to expand
microservices-architect/SKILL.mdOK
22.9%

Tool passed security scan

microservices-architect/references/communication.mdOK
16.7%

Tool passed security scan

Audit Metadata
Max File Score
93%
Classification
KNOWN_SERVER_KNOWN_TOOL_LIST
Files Scanned
6
Files Flagged
4
Chunks Analyzed
12
Analyzed
Mar 7, 2026, 11:42 AM
Security Audit — runlayer — microservices-architect