OpenChainBench Contributor

PassAudited by ClawScan on May 15, 2026.

Overview

This instruction-only contributor guide appears benign, with expected cautions around running repo commands, protecting API keys, and hosting a public metrics endpoint.

Before using this skill, make sure you trust the OpenChainBench repository before running pnpm commands, keep provider API keys out of commits, and review what your public `/metrics` endpoint exposes and costs to operate.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

Low

#ASI04: Agentic Supply Chain Vulnerabilities

What this means

Running dependency installation or build scripts in a cloned repo can execute project code on the user's machine.

Why it was flagged

The skill asks the user to clone an external repository and install project dependencies. This is normal for local contribution validation, but it means the user is trusting that repository and its package scripts.

Skill content

`git clone https://github.com/OpenChainBench/OpenChainBench && cd OpenChainBench` ... `pnpm install`

Recommendation

Review the repository and package scripts before running pnpm commands, and use a normal development sandbox if possible.

Low

#ASI03: Identity and Privilege Abuse

What this means

Improperly scoped or accidentally committed API keys could expose provider accounts or incur costs.

Why it was flagged

The harness may require provider API keys. The instruction is purpose-aligned and explicitly warns not to commit secrets, but credential handling is still security-relevant.

Skill content

Read API keys from environment variables. Never commit them.

Recommendation

Use least-privilege API keys, store them outside the repo, and confirm `.env` files are ignored before committing.

Low

#ASI10: Rogue Agents

What this means

A hosted harness can continue consuming resources and exposing metrics until the user shuts it down or changes access controls.

Why it was flagged

The workflow involves a persistent public service. This is disclosed and central to the benchmark design, but users should understand the ongoing operational exposure.

Skill content

The harness is a long-running data producer... Run continuously and expose `/metrics` over HTTPS on a stable port.

Recommendation

Monitor hosting costs, avoid exposing secrets in metrics, and ensure the harness can be stopped or rotated if needed.