Trust Assessment
amped-defi received a trust score of 88/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, 0 high, 1 medium, and 2 low severity. Key findings include Unpinned npm dependency version, Node lockfile missing, Unpinned or Loosely Pinned Dependencies.
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 | |
|---|---|---|---|---|
| MEDIUM | Unpinned npm dependency version Dependency '@sinclair/typebox' is not pinned to an exact version ('^0.32.0'). Pin dependencies to exact versions to reduce drift and supply-chain risk. | Dependencies | skills/ampedfinance/amped-defi/package.json | |
| LOW | Node lockfile missing package.json is present but no lockfile was found (package-lock.json, pnpm-lock.yaml, or yarn.lock). Commit a lockfile for deterministic dependency resolution. | Dependencies | skills/ampedfinance/amped-defi/package.json | |
| LOW | Unpinned or Loosely Pinned Dependencies Several dependencies in `package.json` use caret (^) version ranges, allowing minor and patch updates. While common, this practice can introduce supply chain risks if a new version of a dependency contains vulnerabilities or breaking changes. For critical applications, exact version pinning is recommended to ensure deterministic builds and prevent unexpected behavior from transitive dependencies. Consider pinning all dependencies to exact versions (e.g., `"package": "1.2.3"`) or using a lockfile (`package-lock.json` or `yarn.lock`) to ensure deterministic dependency resolution across environments. For development dependencies, this might be less critical, but for runtime dependencies, it's a best practice. | LLM | package.json:34 |
Scan History
Embed Code
[](https://skillshield.io/report/40f9fea213c36ad5)
Powered by SkillShield