Caveat verdict

arbitrum-dapp-skill

88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

Development guide for Arbitrum smart contract dApps using documented tooling (Foundry, cargo-stylus, viem); PRIVATE_KEY usage is standard for blockchain deployment and transparently documented.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

33
security
50
transparency
70
maintenance

Permission integrity

Code accesses API keys/tokens but declares no environment variables

credential_access

Findings (4)

Pattern match high

Pipe-to-shell pattern (curl | sh) — supply chain attack vector

README.md · prose · downgraded · curl -L https://foundry.paradigm.xyz | bash

Pattern match high

Pipe to bash — executes piped content as shell commands

README.md · prose · downgraded · | bash

Pattern match medium

Instructs covert action — may act without user awareness

references/frontend-integration.md · prose · downgraded · silently

Pattern match low

Opens WebSocket connection

references/local-devnode.md · prose · downgraded · WebSocket

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class A/B). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.

Permissions & capabilities

No declared permissions — minimal attack surface.

network_incredential_access

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API