DSH Market
A

Axern

by cofy-x · cofy-x/axern

Not a pluginunknownfresh

Open-source sandboxes for AI agents, untrusted code execution, and durable services.

Install Axern

Installs but activates nothing: package.json has no `dsh.bundle` declaration, so `dsh plugin` warns and loads no config layer.

This repository is not a DSH plugin

Its package.json declares no dsh.bundle. In the official docs' own words, a package like this “still installs, but only as a plain dependency: dsh plugin prints a warning and activates no layer”. The install looks like it worked and nothing happens.

What it actually is: Open-source sandboxes for AI agents, untrusted code execution, and durable services. If that is what you came for, use it directly from the repository — it is just not something dsh plugin add can activate.

Before you run it

  • A plugin runs with your permissions once loaded: it can read your files, use your credentials and reach the network. Tool approvals do not sandbox it.
  • Installing from git resolves a moving branch. Pin a commit — github:cofy-x/axern#<commit-sha> — so the code you reviewed is the code you install.

Prerequisites

API key
Not required.
Network access
Not required at runtime.
Language
Go

Install check

Every field the verdict was derived from, so you can re-derive it yourself

Field checkedResultWeightWhat the spec says about it
lifecycleScriptspassinfono install-time scripts
dsh.bundlemissingfatalpackage.json has no `dsh.bundle` key
Verdict reason
no dsh.bundle declaration — installs as a plain dependency only
package.json read
package.json
Rules applied from
docs/user/develop/basic/publish.md
Checked at
2026-08-15

From the README

Excerpt as published by the author, plain text, unedited

Axern is an open-source sandbox platform for AI agents. It isolates untrusted agent-generated code with runsc and runs trusted long-lived services with runc through one resource and lifecycle model. The CLI and the Go, Python, and TypeScript SDKs expose the same public APIs for environments, processes, files, services, storage, tunnels, lifecycle state, and task evidence. > **Project status:** Axern is pre-1.0 and under active development. > It is suitable for evaluation and contribution, but operators should review the security and production boundaries before deploying multi-tenant workloads. The supported local path runs the complete stack with Docker Compose. It needs only the `axern` CLI and Docker Compose v2 — no source checkout, Make, Helm, or language toolchains.

Topics

GitHub topics on this repository

More in Self Hosted Docker Compose

Ranked by similarity inside the cluster, not alphabetically