Semvane

Docs

Semvane platform documentation.

Everything you need to connect repositories, understand API change impact and review Semvane-prepared pull requests. Deeper reference guides expand alongside the platform.

Request access

Getting started

Create an organization, open the Repositories page and install the Semvane GitHub App on your GitHub organization or account, choosing the repositories it may access (a Personal Access Token works too, under Advanced). The repositories sync on their own; run the first scan. The control plane walks you through each step.

App permissions: contents and pull requests (read and write); checks, commit statuses and Actions (read)
Push and CI events arrive through the app's webhook
No long-lived token stored for App connections

API maintenance workflow

Semvane maps the SDKs your repositories use, matches them against its catalog of provider changes, prepares migration plans for affected code and opens draft pull requests in GitHub for your team to review and merge.

Security model

With the GitHub App, Semvane uses installation tokens that expire within an hour, minted per task for one repository; a personal access token, if you connect one instead, is encrypted with ASP.NET Core Data Protection. Every tenant-owned query is scoped to your workspace and fails closed. Sessions use short-lived access tokens with rotating refresh tokens.

Short-lived, per-repository GitHub tokens
Fail-closed tenant isolation
Role-based permissions (Owner, Admin, Developer, Viewer)

Provider coverage

Repositories are synced from GitHub. Usage detection covers Stripe, OpenAI, Shopify, Twilio and Cloudflare SDKs today. Additional providers are added to the catalog incrementally.

Repositories: GitHub
Detection: Stripe, OpenAI, Shopify, Twilio, Cloudflare