Atlas / Skills / kurtosis-tech / Gateway

GatewaySAFE

skills/kurtosis-tech/gateway

A platform for packaging and launching blockchain infra. Think docker compose for blockchain

Verdict
SAFE
Grade
B
Trust score
89 /100
Version
1.0
Hosts
—
License
Apache-2.0
Stars
557
01

Overview

A platform for packaging and launching blockchain infra. Think docker compose for blockchain

Read from source at commit 938b496bbe73OBSERVED · 2026-10-14
Advertisement
02

What it tells the agent

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: gateway
description: Start and manage the Kurtosis gateway for Kubernetes. The gateway forwards local ports to the Kurtosis engine and services running in a k8s cluster. Required when using Kurtosis with Kubernetes. Use when kurtosis engine status shows nothing on k8s or services aren't reachable.
compatibility: Requires kurtosis CLI with Kubernetes cluster access.
metadata:
  author: ethpandaops
  version: "1.0"
---

# Gateway

The Kurtosis gateway creates local port forwards to the engine and services running in a Kubernetes cluster.

## When you need it

The gateway is **required** when running Kurtosis on Kubernetes. Without it, the local CLI cannot reach the engine pod in the cluster.

Not needed when using Docker backend.

## Start the gateway

```bash
# Run in the background
kurtosis gateway &

# Or in a separate terminal
kurtosis gateway
```

## Verify it's working

```bash
kurtosis engine status
```

If this returns engine info, the gateway is working. If it says "No Kurtosis engine is running" but you know the engine pod is up, the gateway isn't running.

## Stop the gateway

```bash
pkill -f "kurtosis gateway"
```

## How it works

The gateway:
1. Finds the engine pod in the `kurtosis-engine-*` namespace
2. Creates a local port forward to the engine's gRPC port
3. When services are accessed, creates additional port forwards to service pods
4. Port mappings shown in `kurtosis enclave inspect` point to localhost via the gateway

## Common issues

| Symptom | Fix |
|---------|-----|
| `No engine running` but engine pod is up | Start the gateway: `kurtosis gateway &` |
| Gateway crashes or disconnects | Restart: `pkill -f "kurtosis gateway"; kurtosis gateway &` |
| Port conflicts | Kill old gateway first: `pkill -f "kurtosis gateway"` |
| Services unreachable after gateway restart | Re-inspect enclave for new port mappings |
03

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codeNA
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
pinned
Secrets in source
none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.

Audited 2026-10-14 · audit v0.4.1 · source sha 938b496bbe73full audit observations/trust-audit/skill/kurtosis-tech__gateway.json · Report an issue / request a re-scan
04

Audit history

Every audit this skill has had.

DateSourceVerdictGradeScoreChange
2026-10-14938b496bbe73SAFEB89first audit
05

Questions

What does the Gateway skill do?

A platform for packaging and launching blockchain infra. Think docker compose for blockchain

Is Gateway safe to install?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.

What can Gateway access on my machine?

The audit observed no filesystem, network or shell use at all in its source.

How current is this page?

The grade is for one exact copy of the source (938b496bbe73), read on 2026-10-14. The repository is watched, and a new audit runs when it changes — this is the first audit.

Advertisement