Versioned security assessment

Report ID: SA-100217D0

6/30/2026, 8:59:23 PM

web3-testing security assessment v2

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
web3-testing
Version
v2
Maintainer
sickn33
Coverage
1 Files scanned · 428 Lines analyzed
Policy version
Unavailable

Confirmed finding summary

No confirmed security findings

The completed audit recorded no confirmed security findings. This is not proof that the Skill has no side effects.

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.

Static analysis found command, network, filesystem, environment, and blocker patterns in SKILL.md. Semantic review shows these are primarily documentation examples for Web3 testing, but the examples do handle private keys, API keys, RPC endpoints, mainnet forks, and CI commands, so users need clear warnings. No prompt injection attempt or confirmed malicious behavior 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

1 Files scanned · 428 Lines analyzed

3 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.

  1. Source

    Binding unavailable

  2. Artifact

    Identity incomplete

  3. Audit

    Complete

  4. 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 4 evidence locations

Filesystem access

May read or write local files.

Not recorded by this audit

Env variables

May read values from the process environment.

Observed in 3 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 3 evidence locations

Capability review items (3)
Medium
Sensitive Credential Handling in Test Configuration Examples
The skill includes examples that read RPC URLs, a private key, CoinMarketCap API key, and Etherscan API key from environment variables. This is common for Web3 tooling, but it can expose funds or service credentials if users copy the pattern into unsafe environments or CI logs.
The cited examples explicitly reference private key and API key environment variables. The context is legitimate testing documentation, so the risk is misuse rather than confirmed exfiltration.
Medium
External Network and Mainnet Fork Usage
The skill demonstrates mainnet forking through external RPC providers and Hardhat network provider requests. This is expected for smart contract testing, but it can send project metadata to RPC providers and consume paid API quotas.
The network behavior is directly shown in mainnet fork and provider request examples. The examples are domain-appropriate and do not show credential exfiltration.
Low
External Command Examples Require User Review
The skill contains shell and CI examples that run Hardhat commands, install dependencies, compile contracts, execute tests, and upload coverage. These are standard developer actions, but users should review generated commands before execution.
The commands are visible documentation examples and are not executed by the skill itself. They still affect local projects or CI when copied by a user.

Risk findings

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

No confirmed security findings were recorded for this completed audit.

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.

Static false positives ignored (1)
Low
Static Filesystem and Blocker Alerts Are False Positives
The reported path traversal at line 168 is a normal Solidity relative import in a test example. The reported C2 and weak-cryptography blocker alerts appear to match ordinary Web3 testing terms and contract-test examples, with no evidence of malicious control channels or weak cryptographic implementation.
The suspicious locations are inside illustrative Solidity and JavaScript test snippets. I found no prompt injection text, command-and-control behavior, or cryptographic algorithm implementation at these locations.

Verify and export

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

Audit attestation: not_attestable