Trust Assessment
usd1transaction received a trust score of 56/100, placing it in the Caution category. This skill has some security considerations that users should review before deployment.
SkillShield's automated analysis identified 5 findings: 1 critical, 0 high, 2 medium, and 0 low severity. Key findings include Missing required field: name, Unpinned npm dependency version, Direct Private Key Input and Usage.
The analysis covered 4 layers: Manifest Analysis, Static Code Analysis, Dependency Graph, LLM Behavioral Safety. All layers scored 70 or above, reflecting consistent security practices.
Last analyzed on February 13, 2026 (commit 13146e6a). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
Behavioral Risk Signals
Security Findings5
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| CRITICAL | Direct Private Key Input and Usage The skill's `handler` function directly accepts a `privateKey` as an input parameter and uses it to authorize a cryptocurrency transfer. Passing raw private keys to an AI agent skill is a severe security risk, as it exposes the key to the LLM's context, potential logging, and the agent's execution environment, making it vulnerable to compromise or accidental exposure. Even with 'secure agent input' recommendations, the fundamental design of handling raw private keys within the skill's logic is highly insecure. Modify the skill to avoid direct handling of private keys. Instead, integrate with a secure key management system (KMS), a hardware security module (HSM), or a secure signing service. The agent should request a signed transaction or an ephemeral, limited-scope credential, rather than the raw private key. If direct signing is unavoidable, ensure the execution environment is highly isolated and audited, and that the private key is never logged or persisted. | LLM | index.js:5 | |
| MEDIUM | Missing required field: name The 'name' field is required for claude_code skills but is missing from frontmatter. Add a 'name' field to the SKILL.md frontmatter. | Static | skills/asgherali/usd1transaction/SKILL.md:1 | |
| MEDIUM | Unpinned npm dependency version Dependency '@wormhole-foundation/sdk' is not pinned to an exact version ('^4.9.1'). Pin dependencies to exact versions to reduce drift and supply-chain risk. | Dependencies | skills/asgherali/usd1transaction/package.json | |
| INFO | Deprecated Transitive Dependency Found The `package-lock.json` file indicates a transitive dependency, `@confio/ics23`, is deprecated. Deprecated packages are no longer maintained and may contain unpatched vulnerabilities, posing a supply chain risk. While it's a transitive dependency, its presence in the lock file suggests it's part of the build. Review the dependency tree to identify if `@confio/ics23` is still required. If so, investigate alternatives or ensure that the functionality it provides is not critical or exposed to untrusted input. Consider updating or removing dependencies that rely on deprecated packages. | LLM | package-lock.json:104 | |
| INFO | Caret Ranges Used for Dependencies in package.json The `package.json` file uses caret (`^`) ranges for its direct dependencies (`@wormhole-foundation/sdk`, `@wormhole-foundation/sdk-base`). While `package-lock.json` pins exact versions, a fresh install without the lock file or an outdated lock file could pull in newer, potentially incompatible or malicious versions if the upstream package is compromised. For high-security contexts, exact pinning is generally preferred. For enhanced security and reproducibility, consider pinning exact versions for all dependencies in `package.json` instead of using caret ranges. Regularly audit and update dependencies to mitigate risks from known vulnerabilities. | LLM | package.json:12 |
Scan History
Embed Code
[](https://skillshield.io/report/7df2cefa44434264)
Powered by SkillShield