@volter/twin-github

GitHub

Version

volter-aiVolter maintainedSelected defaultv3.0.6

Local GitHub repository, issue, pull-request and git workflows over shared synthetic state. REST, GraphQL and Actions scope is documented in the README.

Use GitHub in a World

Keep your app’s real SDK. The World routes this vendor’s configured calls to the selected twin.

Read workflows and limitations Run this twin in your app

Release measurements

HTTP operations served: 94 / 15271433 declared gaps
HTTP operations exercised: Not measured
Installed first use: PassedExact release journey

Measurements describe this release’s recorded scope. Open Evidence for replay, browser results and unexercised operations.

Set up this release

Use Node 22.6 or newer. Install the CLI, then the exact packages shown alongside:

npm install -g @volter/world@3.0.127

In your app’s folder, initialize a World with this implementation:

volter world init --name my-app --twins github --source github=@volter/twin-github

Review the detected vendor and retain the generated bindings. The github service’s source must select this version:

{
  "source": {
    "package": "@volter/twin-github",
    "version": "3.0.6"
  }
}

This is the source field, not a complete config. Keep the installed version, lockfile and generated service source in agreement. Use the release README for throwaway SDK credentials, seeds and limits.

Run your app’s own test command inside the World:

volter world up
volter world run -- npm test
volter world log
volter world down

down stops compute and retains state.

Bring an existing app Recover a failed call Trial an update

Versions and implementations

Package / version	Publisher	Status	First use
@volter/twin-github3.0.5	volter-ai	live	Not measured
@volter/twin-github3.0.6	volter-ai	Selected default	Passed

Evidence for 3.0.6

Installed first use · Passed

Installed first use: Passed
Fresh app installation: Verified
Workflow scope: Exact installed artifact; normal CLI initialization, unchanged SDK, result assertions and retained-state read-only resume where applicable
Customer SDK versions: @octokit/rest@22.0.1
CLI, kernel and runtime versions: @volter/world@3.0.127 · @volter/world-core@3.0.127 · @volter/world-runtime@3.0.127
World clock: {"mode":"wall"}
Retained-state readback: Verified
Stopped compute: Verified
Customer journey failures: 0

API coverage, replay and browser measurements

Counts describe the declared HTTP surface, not separate command tables or other protocols. Consult the release README for those workflows.

Assessment scope: packaged-customer-journey; in-process
Declared HTTP surface: 94 served · 1433 gaps · 1527 declared operations
Exercised HTTP operation coverage: Not measured
Journey steps: 333 answered / 360 steps
Replay: Equal across 2 runs
Journey failures: 0
Browser target: Not measured
HTTP operations exercised through Chromium: Not measured
Chromium journey replay: Not measured
Browser response observation: Not recorded
Application-origin CORS coverage: Not measured
Native cookie-jar coverage: Not measured
DOM coverage: Not measured
Source code coverage: Not measured
State transition coverage: Not measured

Conformance results

decided: 0 failures · every served operation is decided with its demand; every demanded and every refreshed operation is served
published: 0 failures · what a release publishes holds every unit: its manifest, its spec and its journeys
cited: 0 failures · every vendor fact cited is recorded as a page that answered, each quote found on it
refresh: 0 failures · every stored resource of a vendor-backed unit declares how it is read back, and a unit that sends events ingests the vendor's
registered: 0 failures · a vendor-backed unit, lane or not, reaches the registered pack's state system
allowance: 0 failures · a rate budget above the fallback rests on the vendor's documented allowance, cited in its manifest
client: 0 failures · driven by the vendor's own client (its official SDK), served as a World runs it, the vendor's documented behaviour holds · 2 case(s) through the vendor's client
life: 0 failures · the life walked over HTTP against the pack served as a World runs it, with its scenario: every check held
standalone: 0 failures · served by its server.ts as a World runs it, the pack answers HTTP and the boot probe, and each declared socket upgrades

Publisher, admission and provenance

Publisher: volter-ai/twin-packs-open
Source commit: fef33479065926885c79be4a6065dad2c901e9ca
Catalog record commit: b6d0340e190b39e3c63377680b9a589010c3e803
Package integrity: sha512-NNv6Lc3XWjNTqT2l/I+ha8wcnO/7kDtI8+oybYvbngxL389iQc99MvrSIdcdv9AkISrcvIvd8SiQpfsDu16V7w==
Admission mode: Trusted internal publisher · maintainer merge
Catalog assessment: Bundled report checksum verified
Assessed at: Not recorded
Assessment input head: b6d0340e190b39e3c63377680b9a589010c3e803
Evidence: Assessment and admission

Read the catalog snapshot

Install this version

npm install --save-dev --save-exact \
  @volter/world-core@3.0.127 \
  @volter/twin-github@3.0.6

In your app’s folder. Full setup guide

License: Apache-2.0
Node: >=22.3
World kernel: ^3.0.127