Ark

This site is private. Enter the password to continue.

Getting Started
CLI Reference
Package Format
Audit System
Publishing
docs / cli / publish

ark publish

Package your files, attach the audit report, and submit to the Ark registry for review. Packages are live within 24-48h of approval.

Syntax

Usage
ark publish [--dry-run] [--tag <tag>]

Prerequisites

Publish flow

Terminal
$ ark publish

  Reading ark.json...
  ✓ Manifest valid (my-agent@1.0.0)

  Verifying audit report...
  ✓ audit-report.json found (score: 85, hash verified)

  Creating archive...
  ✓ my-agent-1.0.0.tar.gz (18.3 KB)

  Uploading to registry...
  ✓ Submitted

  Package: my-agent@1.0.0
  Status:  pending_review
  ID:      pkg_7f3a2b19c4

  We'll email you at jane@example.com when your package is approved.
  Review typically takes 24-48h.

Dry run

Validate everything without actually submitting. Useful to catch issues before committing.

Terminal
$ ark publish --dry-run

  ✓ Manifest valid
  ✓ Audit report valid (score: 85)
  ✓ Archive would be: 18.3 KB
  → Dry run complete. Nothing submitted.

Publishing a new version

Bump the version field in ark.json, re-run the audit, then publish again. Each version goes through review independently.

ark.json
{
  "name": "my-agent",
  "version": "1.1.0",  ← bump this
  ...
}
Terminal
$ ark audit --full --save
$ ark publish

What gets included in the archive

Everything in the current directory, except:

Security scan: the registry performs an automated secrets scan on every submission. Packages with API keys, passwords, or credentials in plaintext are rejected automatically. Use environment variables or configuration files outside your package directory.