convez.ai
MCP ServerDevOps & InfraestruturaAvançado
szl-holdings

SZL Holdings Platform MCP Server

szl-holdings/platform

MCP server agentic com runtime substrate e workflows CI/CD enterprise

Ver no GitHub
BomPluginScore · de 0 a 100

Monorepo TypeScript com runtime Ouroboros, loops agentic e servidor MCP com 11 ferramentas integradas. Inclui workflows reutilizáveis, gates de CI/CD com Doctrine v11, e provas criptográficas de outcomes. Infraestrutura completa para automação e orquestração de processos.

Instalação

$npx convez-ai szl-holdings/platform

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
87%
Último commit
há 1 dia
Versão
v1.0.0-codex-kernel
Issues abertas
4
Contribuidores
10

Casos de uso

  • Automação de pipelines CI/CD com gates criptográficos
  • Orquestração de workflows agentic com loop feedback
  • Integração de múltiplas ferramentas via MCP server

Veredito

Plataforma enterprise-grade bem estruturada com foco em segurança (SLSA L1, OpenSSF Scorecard, Dependabot). MCP server robusto para cenários de automação complexa, mas requer expertise avançada em TypeScript e arquitetura agentic.

README

A tradução para o português deste README ainda está na fila.

GitHub Surface Map

CI
CodeQL
OpenSSF Scorecard
Dependabot
SLSA
Doctrine

This document explains every file and directory under .github/ so contributors and reviewers know what each piece does and when to touch it.


Architecture

flowchart TD
  MONO[platform monorepo\npnpm + TypeScript]:::in --> RUNTIME[Ouroboros runtime]
  MONO --> FORMULAS[Lutar formulas]
  MONO --> ADAPTERS[Dual-witness adapters]
  RUNTIME --> COV{Covenant Policy\nhuman gate}
  COV --> PROOF[Cryptographic proof\nof every outcome]
  LEAN[(lutar-lean 749/14/163)] -.anchors.-> RUNTIME
  classDef in fill:#0B1F3A,color:#fff,stroke:#00D4FF;

See also: product surfaces · API spec. SLSA L1 honest; Doctrine v11.

Quick Reference

PathPurposeChange when
.github/BRANCH_PROTECTION.mdStep-by-step GitHub UI settings for branch protection, merge rules, environments, secrets, and DependabotCI job names change or new environments are added
.github/CODEOWNERSMaps path patterns to required reviewersNew directories added or ownership changes
.github/copilot-instructions.mdCopilot coding-assistant instructions scoped to this repoCoding conventions change
.github/dependabot.ymlAutomated dependency update schedules for npm, pip, docker, and GitHub ActionsNew package ecosystems added or PR-limit policy changes
.github/profile/README.mdPublic GitHub organization profile (visible at github.com/szl-holdings)Platform branding, product names, or links change
.github/PULL_REQUEST_TEMPLATE.mdDefault PR description template with type, affected surfaces, and quality checklistRequired CI checks or quality gates change
.github/RELEASE_TEMPLATE.mdRelease notes template used by the release.yml workflowRelease format changes
.github/ISSUE_TEMPLATE/Structured issue forms (bug, feature, security redirect)New issue categories needed
.github/assets/Images used by .github/profile/README.mdBrand assets updated
.github/instructions/Editor-level AI coding instructions (gitignored from public mirror)Internal tooling only
.github/workflows/All GitHub Actions workflowsCI/CD pipeline changes

Workflows

Core CI (required for every PR)

WorkflowTriggerRequired CheckPurpose
ci.ymlPR + push to main/masterCI GateAggregate gate: lint, typecheck, test, build, integration tests, secret scan, readiness smoke, proof-chain, route security
ci.ymlPR + push to main/masterReadiness Gate (smoke:product-mode)Product-mode API smoke test surfaced separately for fast PR visibility
e2e.ymlPR + push to main/masterE2E GateFull Playwright matrix across all artifact surfaces + axe-core a11y
dependency-review.ymlPR onlydependency-reviewOSS vulnerability scan on changed dependencies
codeql.ymlPR + push + weekly scheduleanalyzeGitHub CodeQL static analysis (JavaScript/TypeScript)

Security (advisory / scheduled)

WorkflowTriggerPurpose
security.ymlPR + pushDependency vulnerability scan + SBOM generation
secret-scan-scheduled.ymlDaily 06:17 UTC + .gitleaks.toml changesFull-history Gitleaks scan against main; uploads SARIF to Security tab and opens triage issue on findings
secret-scan.ymlPR onlyPR-diff Gitleaks scan using .gitleaks.toml

Build & Quality (advisory)

WorkflowTriggerPurpose
lighthouse.ymlPR + pushLighthouse CI performance/a11y/SEO scores — advisory only (continue-on-error: true; not a blocking required check)
readme-qa.ymlPR + pushValidates README image paths, badge workflow names, and link integrity
verify-source-of-truth.ymlPR + pushChecks canonical doc sources are in sync
audit-full.ymlManual dispatchFull audit suite (mocks, routes, deps, copy, design)
commitlint.ymlPREnforces Conventional Commits format
a11y.ymlPR + pushAxe-core accessibility checks (advisory)
build.ymlPR + pushExplicit per-artifact build validation

Release & Deploy

WorkflowTriggerPurpose
release.ymlPush to mainDetermines semver bump from commit prefixes, creates Git tag, publishes GitHub Release
deploy-staging.ymlPush to mainDeploys to staging environment automatically
deploy-production.ymlPublished releaseDeploys to production environment (requires reviewer approval)
container-publish.ymlPublished releaseBuilds and publishes Docker images
npm-publish.ymlPublished releasePublishes public packages to npm

Operations

WorkflowTriggerPurpose
backup.ymlNightly cronDatabase backup and remote upload (Azure Blob). Failure triggers the backup-upload-stalled runbook in INCIDENT_RESPONSE.md
uptime-monitor.ymlScheduled + manualChecks production endpoints are reachable
prism-counsel-ci.ymlPR + pushCI for the legacy PRISM Counsel domain API routes (retained for backward compat)

Issue Templates

FileTypeNotes
ISSUE_TEMPLATE/bug_report.ymlBug reportStructured form: surface, severity, repro steps, environment
ISSUE_TEMPLATE/feature_request.ymlFeature requestStructured form: problem statement, proposed solution, priority
ISSUE_TEMPLATE/security_report.mdSecurity disclosureRedirects to security@szlholdings.com — do not open public issues for vulnerabilities
ISSUE_TEMPLATE/config.ymlTemplate configDisables blank issues; routes security reports off-Issues to email

Dependency Update Policy

Dependabot is configured in dependabot.yml with the following schedule and limits:

EcosystemDirectoriesSchedulePR LimitGrouping
npmRoot (all pnpm workspaces)Weekly (Mon 09:00 ET)10React, Vite, testing, TypeScript, UI, DB, TanStack
pipworkers/substrate-python, services/substrate-py-workers, services/lyte-metrics-store, scripts/mediaWeekly (Mon 09:00 ET)3 per dirNone (low volume)
dockerartifacts/api-server, artifacts/szl-holdings, artifacts/vessels, artifacts/terra, artifacts/carlota-joWeekly (Mon 09:00 ET)3 per dirNone (low volume)
github-actionsRootWeekly (Mon 09:00 ET)5actions/*, github/*, CI tooling

All Dependabot PRs must pass the same required CI checks as any other PR.

Note — docs/github/packages/maven/pom.xml: This file is a documentation template for future Java/Kotlin consumers of the GitHub Packages registry (its header says "Copy this file to your package directory"). It is not an active production manifest. No Maven Dependabot entry is needed until an actual Java/Kotlin package is added to the repo.


Secret Scanning

Two complementary layers:

  1. PR-time gate (ci.yml → secret-scan job + secret-scan.yml): Gitleaks scans the PR diff using .gitleaks.toml. Blocks merge on any finding.
  2. Scheduled sweep (secret-scan-scheduled.yml): Full-history Gitleaks scan of main every day at 06:17 UTC. Uploads SARIF to the Security tab; opens a triage issue on findings.

Config lives in .gitleaks.toml. If you need to add an allowlist entry, document the reason inline and keep patterns as narrow as possible.

If a real leaked secret is discovered: do NOT rotate from a PR. File a high-priority follow-up task and add an entry to INCIDENT_RESPONSE.md under the "Suspected secret exposure" runbook.


Branch Protection Summary

See BRANCH_PROTECTION.md for the full GitHub UI configuration checklist. Required status checks for main:

  • CI Gate
  • Readiness Gate (smoke:product-mode)
  • E2E Gate
  • dependency-review
  • analyze

The Lighthouse Gate (advisory) check is not a required check — it runs advisory-only with continue-on-error: true.

Ver o original no GitHub

Bom para

Relacionados