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.
01
Evidence chain
Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
04
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.
05
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.