Trust Assessment
autonomous-agent received a trust score of 75/100, placing it in the Mostly Trusted category. This skill has passed most security checks with only minor considerations noted.
SkillShield's automated analysis identified 3 findings: 0 critical, 1 high, 2 medium, and 0 low severity. Key findings include Unpinned npm dependency version, Direct Private Key Configuration, Unpinned Dependencies in package.json.
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 Findings3
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| HIGH | Direct Private Key Configuration The skill's setup instructions explicitly mention configuring `EVM_PRIVATE_KEY` directly, likely as an environment variable or in a configuration file. Storing private keys in this manner is highly insecure and creates a significant attack surface for credential harvesting if the skill's implementation is compromised or malicious. While the provided documentation does not show the code handling the key, the instruction itself signals a high-risk practice. Avoid configuring private keys directly in environment variables or plain text files. Instead, recommend using secure key management solutions such as hardware security modules (HSMs), encrypted keystores, or cloud key management services (KMS). If direct private key input is unavoidable, ensure robust security measures are in place to prevent logging, exfiltration, or unauthorized access. | LLM | SKILL.md:204 | |
| MEDIUM | Unpinned npm dependency version Dependency '@langchain/core' is not pinned to an exact version ('^0.3.0'). Pin dependencies to exact versions to reduce drift and supply-chain risk. | Dependencies | skills/josephrp/autonomous-agent/package.json | |
| MEDIUM | Unpinned Dependencies in package.json The `package.json` file uses caret (`^`) version ranges for all its dependencies. While `package-lock.json` pins specific versions for reproducible builds, relying on caret ranges in `package.json` can introduce supply chain risks. If a malicious update is published within the allowed range, or if the `package-lock.json` is not strictly used (e.g., in some CI/CD pipelines or fresh installs), the skill could inadvertently pull in a compromised or incompatible dependency. Consider using exact version pinning (e.g., `"package": "1.2.3"`) or stricter version ranges (e.g., `"package": "~1.2.3"` for patch-only updates) for all dependencies, especially critical ones. This provides greater control over dependency versions and reduces the risk of unexpected or malicious updates. | LLM | package.json:39 |
Scan History
Embed Code
[](https://skillshield.io/report/97f2b757de2096ca)
Powered by SkillShield