OpenClaw BaseCred SDK

PassAudited by ClawScan on May 10, 2026.

Overview

This is a coherent read-only reputation lookup skill; it uses optional API keys and an npm SDK, but the provided artifacts do not show hidden, destructive, or purpose-mismatched behavior.

Before installing, confirm you trust the npm dependency chain, use the lockfile if available, and provide only the optional API keys needed for Talent Protocol or Farcaster lookups.

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.

Info

#ASI02: Tool Misuse and Exploitation

What this means

Addresses you check may be sent to the listed third-party reputation services.

Why it was flagged

The skill sends the checked Ethereum address to external reputation providers through the BaseCred SDK. This is the core advertised function and is disclosed in the documentation.

Skill content

const profile = await getUnifiedProfile(address, config); ... baseUrl: options.ethosUrl || 'https://api.ethos.network' ... baseUrl: options.talentUrl || 'https://api.talentprotocol.com'

Recommendation

Use it only for addresses you are comfortable querying through those providers, and review provider privacy/API terms if that matters to your use case.

Low

#ASI03: Identity and Privilege Abuse

What this means

The Node process and its SDK dependency can access the optional provider API keys loaded for the lookup.

Why it was flagged

The skill loads the user's OpenClaw .env file and uses optional Talent Protocol and Neynar API keys. This credential use is disclosed and aligned with fetching those providers' data.

Skill content

const openclawEnvPath = join(homedir(), '.openclaw', '.env');
dotenv.config({ path: openclawEnvPath }); ... process.env.TALENT_API_KEY ... process.env.NEYNAR_API_KEY

Recommendation

Use limited-scope API keys, keep ~/.openclaw/.env permission-restricted, and rotate keys if you suspect they were exposed.

Low

#ASI04: Agentic Supply Chain Vulnerabilities

What this means

A future compatible dependency update could alter how API calls or credentials are handled.

Why it was flagged

The skill relies on npm dependencies, including the BaseCred SDK that performs provider integration. This is expected, but the package.json uses semver ranges, so dependency behavior can change if installed without respecting the lockfile.

Skill content

"dependencies": {
  "@basecred/sdk": "^0.6.2",
  "dotenv": "^16.3.1"
}

Recommendation

Install with the included lockfile where possible, verify the resolved @basecred/sdk version, and re-audit before upgrading dependencies.