Is Session Orchestrator safe and trustworthy?

tashan scores Session Orchestrator on public evidence — tashan score 65.0/100, it is currently active. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Session Orchestrator?

Configure it from its source repository — it is a remote / registry server.

Who maintains Session Orchestrator?

4 GitHub contributors, source: Kanevry/session-orchestrator.

‹ The Index

Session Orchestrator

plugin

Session-level orchestration for Claude Code - structures development work into 5 typed waves (Discovery → Core → Polish → Quality → Finalization) with parallel subagent execution, inter-wave quality gates, and verified close-out. Auto-detects GitLab or GitHub from your git remote for full VCS lifecycle support. Three commands replace manual session management: /session starts with project analysis, /go executes the wave plan, /close verifies and commits.

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code

Category: Productivity — see all ranked ›

Work: Agent configuration · Project management

Who it is for: Agent operator · Product manager · Operations

solid

“Hook enforcement is full only on Claude Code; ships a seven-field minimum config”

tashan score: 65.0
Expertise: 79.0 (solid)
Adoption: 1 repos
Health: active
GitHub stars: 48
Contributors: 4
License: MIT

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

source ↗ · plugin:kanevry/session-orchestrator/session-orchestrator

Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›