Design the pipeline. Verify the outcome.
Multi-provider CI/CD analysis, intent contracts and safe CI scaffolding inside Visual Studio Code.
Quick start · Features · Screenshots · Limitations · Development · Contributing
A pipeline can be valid YAML and still be unsafe, fragile or incorrect for its intended purpose. Orquestivo is an open-source, local-first VS Code extension that inspects CI/CD pipelines, checks them against what you say they must achieve, and generates conservative CI starting points.
Current version: 0.2.0 (pre-1.0). Published to the Visual Studio Marketplace and Open VSX. See CHANGELOG.md and ROADMAP.md. Known gaps (real GitHub E2E, WSL/SSH/Dev Containers checks, manual accessibility audit) are tracked honestly in RELEASE_READINESS.md.
Orquestivo reports static inference by default. It does not run your pipeline. Only opt-in, read-only evidence from real GitHub Actions runs can back a statement about what actually happened, and even then it does not prove business requirements are met.
- Pick the project. The Control Center shows the project being audited (a single folder is selected automatically). With several folders or a monorepo press Change project; the choice is remembered per workspace and "entire workspace" is a deliberate option.
- Press Analyze existing CI/CD. Analysis is local and read-only: no pipeline is run and no GitHub login, token or AI is needed. Prefer a new pipeline? Use Create new CI.
- Read the review. The status is honest (Needs attention, Partial, No problems detected by the available rules, No CI/CD found or Not evaluated) and What to fix first lists the most important items with why they matter and what to change.
- Apply a safe fix, or fix it by hand. For a small set of verified fixes press Review and apply fix: Orquestivo opens a diff, asks for explicit confirmation, refuses to write if the file changed meanwhile, re-analyzes, and Undo last improvement reverts it unless you edited the file afterwards (the undo record survives reloading VS Code). Verified fixes: GitHub Actions
permissionsand jobtimeout-minutes; GitLab CI defaulttimeoutand artifactexpire_in; Azure PipelinestimeoutInMinutes; JenkinstimeoutandbuildDiscarderoptions. Every other item is manual guidance, with no apply button.
The Control Center is organised in tabs: Summary, Findings, Improvements, Pipeline, Evidence and Advanced. Refreshes keep your tab, focused control, scroll position and expanded sections.
| Area | Capability |
|---|---|
| Project-aware audit | Project selector (multi-root, monorepo sub-projects), results, intent contract and generator default scoped to the selected project; stale scans are discarded when you switch |
| Guided improvements | Prioritised plan from real findings; verified diff-first fixes for seven rules across GitHub Actions, GitLab CI, Azure Pipelines and Jenkins, each re-analyzed before it is offered, with hash guard and persistent undo. No fix is invented for any other rule |
| Script-injection checks | Flags attacker-controlled values (github.head_ref, inputs.*, issue and pull request text, workflow_run data) interpolated into run scripts and actions/github-script programs, even inside format() or bracket access. Textual, no data-flow: see docs/ANALYSIS.md |
| Multi-provider analysis | GitHub Actions (69 rule codes), GitLab CI/CD, Azure Pipelines and Jenkins (declarative Jenkinsfile). Rule details: docs/ANALYSIS.md, docs/PROVIDERS.md |
| Control Center | Webview with an accessible pipeline diagram (with a textual alternative) and three explanation levels: beginner, advanced, expert |
| Intent contracts | .orquestivo/intent.json states what the pipeline must achieve; each criterion yields PASS / FAIL / WARN / SKIP / INCONCLUSIVE / BLOCKED. See docs/EVIDENCE.md |
| Run evidence (opt-in) | Read-only GitHub Actions run metadata, with a token kept in VS Code SecretStorage. Off until you connect |
| Generator wizard | Presets node, typescript, react, next, go, python, java-maven, java-gradle, php, docker; diff preview before writing and undo of the last generation. See docs/GENERATOR.md |
| Optional AI | Disabled by default; no provider is bundled. Suggestions are hypotheses and never produce PASS. See docs/AI.md |
| Native integration | Findings in Problems, the Activity Bar tree and the Control Center |
| Localize | English and Spanish UI shell; full rule-message localization is still in progress |
Commands (Command Palette, category "Orquestivo"):
| Command ID | Purpose |
|---|---|
orquestivo.analyze |
Analyze CI pipeline files in the workspace |
orquestivo.selectProject |
Choose which project (folder, monorepo sub-project or whole workspace) is audited |
orquestivo.undoImprovement |
Undo the last applied improvement (refuses if the file was edited afterwards) |
orquestivo.generateCI |
Open the generator wizard |
orquestivo.openHome |
Open the Control Center |
orquestivo.connectGitHub |
Store a GitHub token in SecretStorage (opt-in) |
orquestivo.disconnectGitHub |
Delete the stored token |
orquestivo.fetchRuns |
Fetch recent run evidence from GitHub (opt-in) |
orquestivo.undoLastGeneration |
Undo the files created by the last generation |
orquestivo.ai.explainFinding |
Ask the configured AI provider to explain a finding (only if enabled) |
Command registration and UI wording were being implemented while this document was written. Cross-check the live list in
package.json(contributes.commands).orquestivo.openFindingandorquestivo.improveFindingare internal commands used by the Control Center.
Diagnostics identify supported static patterns. A clean scan does not mean a pipeline has run, is secure in every context or will deploy successfully.
A look at Orquestivo. Images 1–3 are real VS Code captures from the earlier 0.1.0 release; images 4–11 show the current Control Center, rendered from the product's own HTML (src/ui) with a real analysis of sample workflows and a VS Code dark theme palette. They are not full VS Code window captures; regenerate them with scripts/render-readme-media.mjs. Click any image to open it at full resolution.
The Control Center summarizes analyzed workflow files, errors, warnings and informational findings. It also lists rule identifiers and source locations for investigation.
Control Center · Resumen de análisis y hallazgos
Open the workflow YAML and inspect issues alongside the native Problems panel. Orquestivo findings can coexist with diagnostics from other installed GitHub Actions or YAML extensions.
Diagnostics · Errores y advertencias contextualizados en el editor
Use Orquestivo: Generate safe CI workflow to select a project stack. Orquestivo previews the YAML and asks for confirmation before creating the workflow.
CI generator · Selección del stack del proyecto
Counts by severity, filters by severity and category, and each finding with why it matters, what to do, its rule, evidence state and documentation link. The Advanced experience level is shown; Beginner and Expert present the same data differently.
Control Center · Resumen, filtros y hallazgos explicados
An accessible diagram built from the needs graph: focusable nodes with their YAML line, and a text alternative for screen readers. It shows static structure only and never invents execution states.
Diagrama · Jobs y dependencias, sin estados de ejecución inventados
Declare what the pipeline must guarantee in .orquestivo/intent.json. Each criterion gets a verdict (PASS, FAIL, WARN, SKIP, INCONCLUSIVE, BLOCKED) and its basis. Only PASS counts as met, and static inference is never presented as proof that something ran.
Intención y evidencia · Veredictos con su base de evidencia
A pull request workflow that interpolates github.head_ref, a dispatch input and a pull request body into a shell script and a github-script program. Each occurrence is reported with its line, the exact untrusted value and the safe alternative (pass it through env); the self-hosted runner under pull_request is flagged as well. The Security category filter is applied.
Seguridad · Valores no confiables interpolados en scripts
GitHub Actions, GitLab CI/CD and Jenkins files analysed together: provider chips, severity and category counts across all files, and findings grouped by file.
Multi-proveedor · Un solo análisis para varios CI
Images 1–3 predate the multi-provider Control Center, the wizard diff preview and the evidence features. None of these images demonstrates execution, deployment or verification of a pipeline's intended outcome; the guided wizard and the Problems panel in a real VS Code window are covered by the integration suite rather than by a screenshot.
For an existing project, the Summary tab ranks the findings by priority and says where each one is, why it matters and what to change. Items that have a verified automatic fix offer Review and apply fix; a diff is shown first and nothing changes until you confirm. The Beginner experience level is shown.
Resumen · Qué corregir primero, con arreglos que se revisan antes de aplicar
When the selected project has no supported pipeline file, the Control Center says so and offers to create one with the guided generator.
Proyecto sin CI · Invitación a crear uno nuevo
When no folder is open, the Control Center says so, offers Open project and reports the review as not evaluated instead of showing an empty result.
Sin carpeta · Selección de proyecto
The diff-first fix preview opens in VS Code's own diff editor, not in the Control Center, so it is not part of this gallery; it is covered by the integration suite.
Install Orquestivo (publisher armotusitio) from the Visual Studio Marketplace or Open VSX. To try a build from source instead, build the VSIX locally with npm run package.
Prerequisites: VS Code 1.99+, Node.js 22+ and npm. For analysis, open a trusted repository that contains pipeline files.
git clone https://github.com/Drako01/orquestivo.git
cd orquestivo
npm ci
npm run packageIn VS Code, select Extensions → ··· → Install from VSIX… and choose orquestivo.vsix. Then open a trusted project and:
- Run Orquestivo: Analyze — scans supported pipeline files and publishes diagnostics.
- Click the Orquestivo Activity Bar icon or run Orquestivo: Open Control Center.
- Optionally run the generator wizard to create a starter workflow after reviewing the diff.
Step-by-step guides: docs/USAGE.md. Problems: docs/TROUBLESHOOTING.md.
If you install a VSIX from a CI run or a GitHub Release, verify the SHA-256 next to it with node scripts/vsix-checksum.mjs check orquestivo.vsix. Orquestivo is not an enterprise-certified product.
| Evidence | What it establishes |
|---|---|
| YAML / Groovy parsed | Syntax was understood by the parser |
| Static analysis completed | Supported rules were evaluated |
| Remote run evidence (opt-in) | A real runner reported that run/job conclusion; only for GitHub Actions |
| Intended outcome verified | Needs explicit criteria in an intent contract and matching evidence; many criteria stay INCONCLUSIVE or BLOCKED by design |
Verdict aggregation: FAIL > BLOCKED > INCONCLUSIVE > WARN > SKIP > PASS. An aggregate is PASS only if every verdict is PASS. An unavailable connector yields BLOCKED, never PASS.
- Static first. No pipeline command is ever executed by Orquestivo. Expressions, matrices and provider schemas are not exhaustively validated; included/templated files (GitLab
include, Azure templates, Jenkins shared libraries) are not resolved. - Jenkins support is a bounded tokenizer of declarative pipelines, not a Groovy interpreter. Scripted pipelines are out of scope.
- Remote evidence is GitHub Actions only, opt-in, read-only, and its real-network end-to-end test is BLOCKED without credentials (see docs/EVIDENCE.md).
- No bundled AI. AI is off by default and the repository ships no network code or provider SDK for it. Suggestions are never evidence.
- Workspace Trust matters. Analysis and generation require a trusted workspace; reads are bounded.
- Environments. CI covers Linux (full gate and real VS Code), Windows and macOS (platform gate). WSL, Remote SSH, Dev Containers, multi-root and monorepos are not yet manually verified: docs/COMPATIBILITY.md.
- Static injection checks.
EXPRESSION_IN_SCRIPTfollows a fixed list of untrusted contexts and does not track values copied throughsteps.*.outputsorneeds.*.outputs. A clean scan is not a security guarantee. - Single maintainer. One owner approves pull requests and merges them through the ruleset bypass. Merging a release to
mainpublishes it automatically, after the strict gate re-run inpublish.yml; the Environments only accept deployments frommain, and the gate verifies that configuration (docs/RELEASE.md). OIDC trust in the registries is registry-side and cannot be verified from the repository.
Related: Security, Privacy, Threat model, Security audit, Architecture, Roadmap.
No telemetry. Nothing leaves your machine unless you opt in: connecting GitHub (token in SecretStorage) enables read-only requests to the GitHub API, and AI (off by default) requires explicit per-provider consent with a redacted disclosure. Details: PRIVACY.md.
npm ci
npm run verify:fast # typecheck, lint, unit tests (daily loop)
npm run verify:enterprise # full gate with per-step status and reports/
npm run build && npm run test:integration # real VS Code Extension Host (downloads VS Code)
npm run bench # scan latency baseline (see docs/TESTING.md)
npm run package # builds orquestivo.vsixverify:fast is the local loop; verify:platform is what Windows and macOS CI run; verify:release is the strict, uncached gate. A partial run is INCONCLUSIVE, and npm audit without network is BLOCKED, never PASS. See docs/TESTING.md and docs/DEVELOPMENT.md.
Architecture summary: provider-neutral core in src/core/ (analyzer, PipelineModel, generator, evidence, intent), CI dialects in src/providers/, cross-cutting safety in src/security/, optional AI contracts in src/ai/, and a thin VS Code layer in src/extension.ts. Core modules never import vscode. See ARCHITECTURE.md.
This project targets Enterprise AAAA engineering practices, but this is an objective, not a current certification. Open gates are listed in RELEASE_READINESS.md; the plan is in ROADMAP.md and the release process. Publication is manual and requires maintainer approval.
Contributions are welcome — ¡Se aceptan contribuciones! Developers, DevOps engineers, QA specialists, translators, designers and accessibility reviewers can help.
Start with CONTRIBUTING.md (setup, adding a rule, provider or preset, tests, commit convention) and the Code of Conduct.
- Open an issue for a reproducible bug or a scoped enhancement.
- Review the roadmap to find unimplemented capabilities.
- Open a pull request against
mainonce your branch and tests are ready. Do not commit secrets or private CI logs.
For functional issues, use GitHub Issues or ArmoTuSitio support (see SUPPORT.md). Report vulnerabilities privately, following SECURITY.md; do not open public issues containing exploit details, tokens or confidential pipeline data.
Distributed under the MIT License. See LICENSE.
Designed and developed by Alejandro Daniel Di Stefano
© 2026 ArmoTuSitio · Open source under the MIT License
Release checks run only on PR; after merging to main, publish reuses the exact CI-tested VSIX with source-tree provenance and SHA-256, no rerun. See docs/RELEASE.md.
