Versioned security assessment

Report ID: SA-826529A8

7/10/2026, 12:01:28 AM

openserv-launch security assessment v1

Skill Security Certification Report

Audit History

Audit model: codex Historical report

Skill name: openserv-launch
Version: v1
Maintainer: internet-court
Source: github.com/internet-court/internet-court-skill/tree/main/vendored/openserv/openserv-launch
Coverage: 7 Files scanned · 1,308 Lines analyzed
Policy version: Unavailable

Highest confirmed finding severity

High

2 confirmed security findings require attention.

Installation context

Historical evidence

This report may not describe the currently installable artifact. Open the current Skill page for install guidance.

Open current Skill page

This report does not block or authorize the manifest or ZIP.

Most high-risk static alerts are false positives from TypeScript template literals, Markdown code fences, and token locker terminology. The real risks are intentional external OpenServ API calls, public Base Mainnet launch side effects, and unpinned remote update commands. No evidence of prompt injection, ransomware behavior, filesystem abuse, or secret exfiltration was found.

Report position

Historical report

Open audit history before using this report to install.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

7 Files scanned · 1,308 Lines analyzed

23 items shown for review

Limitations

This report does not claim runtime or sandbox execution and does not prove the absence of side effects.

Evidence chain

Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.

Source

Binding unavailable
Artifact

Identity incomplete
Audit

Complete
Install contract

Open manifest to verify
Open manifest

Capabilities observed

Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.

Contains scripts

May execute code included with the Skill.

Not recorded by this audit

Network access

May connect to external services.

Observed in 47 evidence locations

Filesystem access

May read or write local files.

Observed in 1 evidence location

Env variables

May read values from the process environment.

Observed in 5 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 50 evidence locations

Capability review items (21)

Medium

examples/agent-launcher.ts:59

HTTP client library

const response = await axios.post(`${API_BASE}/api/launch`, args, {

This sends token metadata and wallet information to the external OpenServ launch API. The request is intentional, but it can trigger public blockchain launch side effects.

Medium

examples/launch-token.ts:67

HTTP client library

const response = await axios.post<LaunchResponse>(`${API_BASE}/api/launch`, request, {

This sends token metadata and wallet information to the external OpenServ launch API. The request is intentional, but it can trigger public blockchain launch side effects.

Medium

reference.md:32

Hardcoded URL

curl -X POST "https://instant-launch.openserv.ai/api/launch" \

This hardcoded OpenServ launch endpoint is used for an external POST that can create public Base token assets. The endpoint is documented, but the side effect is material.

Medium

SKILL.md:42

HTTP client library

const response = await axios.post('https://instant-launch.openserv.ai/api/launch', {

This sends token metadata and wallet information to the external OpenServ launch API. The request is intentional, but it can trigger public blockchain launch side effects.

Medium

SKILL.md:171

HTTP client library

const response = await axios.post('https://instant-launch.openserv.ai/api/launch', args)

This sends token metadata and wallet information to the external OpenServ launch API. The request is intentional, but it can trigger public blockchain launch side effects.

Medium

SKILL.md:42

Hardcoded URL

const response = await axios.post('https://instant-launch.openserv.ai/api/launch', {

This hardcoded OpenServ launch endpoint is used for an external POST that can create public Base token assets. The endpoint is documented, but the side effect is material.

Medium

SKILL.md:171

Hardcoded URL

const response = await axios.post('https://instant-launch.openserv.ai/api/launch', args)

This hardcoded OpenServ launch endpoint is used for an external POST that can create public Base token assets. The endpoint is documented, but the side effect is material.

Medium

troubleshooting.md:142

Hardcoded URL

curl -X POST "https://instant-launch.openserv.ai/api/launch" \

This hardcoded OpenServ launch endpoint is used for an external POST that can create public Base token assets. The endpoint is documented, but the side effect is material.

Low

examples/agent-launcher.ts:114

HTTP client library

const response = await axios.get(`${API_BASE}/api/tokens?${params.toString()}`)

This performs an outbound GET request to the OpenServ token API. It is expected behavior, but it still sends query or address data to an external service.

Low

examples/agent-launcher.ts:144

HTTP client library

const response = await axios.get(`${API_BASE}/api/tokens/${args.address}`)

This performs an outbound GET request to the OpenServ token API. It is expected behavior, but it still sends query or address data to an external service.

Low

examples/agent-launcher.ts:22

Hardcoded URL

const API_BASE = 'https://instant-launch.openserv.ai'

This hardcoded OpenServ API URL directs traffic to an external service. The endpoint is expected for the skill, but it should be disclosed to users.

Low

examples/launch-token.ts:19

Hardcoded URL

const API_BASE = 'https://instant-launch.openserv.ai'

This hardcoded OpenServ API URL directs traffic to an external service. The endpoint is expected for the skill, but it should be disclosed to users.

Low

examples/list-tokens.ts:65

HTTP client library

const response = await axios.get<TokensResponse>(url)

This performs an outbound GET request to the OpenServ token API. It is expected behavior, but it still sends query or address data to an external service.

Low

examples/list-tokens.ts:70

HTTP client library

const response = await axios.get(`${API_BASE}/api/tokens/${address}`)

This performs an outbound GET request to the OpenServ token API. It is expected behavior, but it still sends query or address data to an external service.

Low

examples/list-tokens.ts:17

Hardcoded URL

const API_BASE = 'https://instant-launch.openserv.ai'

This hardcoded OpenServ API URL directs traffic to an external service. The endpoint is expected for the skill, but it should be disclosed to users.

Low

reference.md:113

Hardcoded URL

curl "https://instant-launch.openserv.ai/api/tokens"

This hardcoded OpenServ API URL directs traffic to an external service. The endpoint is expected for the skill, but it should be disclosed to users.

Low

reference.md:116

Hardcoded URL

curl "https://instant-launch.openserv.ai/api/tokens?creator=0x1234..."

This hardcoded OpenServ API URL directs traffic to an external service. The endpoint is expected for the skill, but it should be disclosed to users.

Low

reference.md:119

Hardcoded URL

curl "https://instant-launch.openserv.ai/api/tokens?limit=10&page=2"

This hardcoded OpenServ API URL directs traffic to an external service. The endpoint is expected for the skill, but it should be disclosed to users.

Low

reference.md:176

Hardcoded URL

curl "https://instant-launch.openserv.ai/api/tokens/0xabcdef1234567890abcdef1234567890abcdef12"

This hardcoded OpenServ API URL directs traffic to an external service. The endpoint is expected for the skill, but it should be disclosed to users.

Low

SKILL.md:34

HTTP client library

npm install axios

The documentation instructs a package-manager install that performs external network activity. This is common setup, but users should review dependency installation in untrusted contexts.

Low

SKILL.md:16

Hardcoded URL

**Base URL:** `https://instant-launch.openserv.ai`

This hardcoded OpenServ API URL directs traffic to an external service. The endpoint is expected for the skill, but it should be disclosed to users.

Risk findings

Confirmed security concerns are separated from items that still need review.

Confirmed security concerns (2)

RISK-001 High

examples/agent-launcher.ts:26-33 examples/agent-launcher.ts:57-60

Automated Token Launch Without Explicit Confirmation

The agent example tells the assistant to collect launch fields and call the launch capability, and the capability posts directly to the launch API. This can create public Base Mainnet assets without a shown final approval gate.

The cited code directly connects an agent capability to POST /api/launch after collecting user fields. No explicit confirmation step appears in the example before the external launch call.

RISK-002 Medium

SKILL.md:215-226

Unpinned Remote Skill Update Commands

The skill instructs users to run npx-based skill update and add commands. These commands can fetch remote packages and alter installed skill state without a pinned version or integrity check.

The instructions show npx skills update and npx skills add commands. The risk is supply-chain exposure from remote command execution, although the commands appear to be maintenance guidance.

Remediation

Suggested fixes recorded by this audit. Applying them is the maintainer’s responsibility.

FIX-001
High
Token launches can occur through the agent example without a shown final approval gate.

Add an explicit confirmation step before POST /api/launch, showing token metadata, wallet, endpoint, and Base Mainnet consequences.
FIX-002
Medium
The skill relies on external OpenServ API calls for launch and token lookup workflows.

Document every outbound endpoint and require users to verify the destination before sending launch metadata.
FIX-003
Medium
The update section uses unpinned npx commands that can change installed skills.

Pin tool versions or link to verified installation guidance with integrity expectations.
FIX-004
Low
Example files reference environment variables for wallet and API key configuration.

Keep env.example as placeholders only and warn users not to commit real .env files.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit: Unavailable
Content hash: Unavailable
Tree hash: Unavailable
Skill path: Unavailable
Audit payload hash: Unavailable

Analysis metadata

Audit model: codex

Analysis state: Complete

Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.

Verify and export

JSON report CITATION.cff SARIF 2.1.0 Signed installation manifest

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable