Trust Assessment
apex received a trust score of 93/100, placing it in the Trusted category. This skill has passed all critical security checks and demonstrates strong security practices.
SkillShield's automated analysis identified 3 findings: 0 critical, 0 high, 1 medium, and 2 low severity. Key findings include Unpinned npm dependency version, Unpinned Dependencies in package.json, Outdated lockfileVersion in package-lock.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 14, 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 'bignumber.js' is not pinned to an exact version ('^9.1.2'). Pin dependencies to exact versions to reduce drift and supply-chain risk. | Dependencies | skills/joshlin111/apex-trading/scripts/package.json | |
| LOW | Unpinned Dependencies in package.json The 'package.json' file uses caret (^) ranges for 'bignumber.js' and 'node-fetch' dependencies. This allows minor and patch version updates, which can introduce unexpected changes or potential vulnerabilities if a malicious update is published. For security-sensitive applications, pinning exact versions is often preferred to ensure deterministic builds and reduce supply chain risks. Pin exact versions for all dependencies (e.g., "bignumber.js": "9.1.2") or use a lockfile with a modern version (lockfileVersion 2 or 3) to ensure deterministic builds. | LLM | scripts/package.json:5 | |
| LOW | Outdated lockfileVersion in package-lock.json The 'package-lock.json' file uses 'lockfileVersion: 1'. This older version is known to have issues with determinism and can sometimes lead to different dependency trees being installed compared to newer lockfile versions (2 or 3). While not a direct vulnerability, it increases the risk of inconsistent builds and potential supply chain issues. Upgrade the 'package-lock.json' to a newer version (e.g., by running 'npm install --package-lock-only' with a recent npm version) to benefit from improved determinism and security features. | LLM | scripts/package-lock.json:3 |
Scan History
Embed Code
[](https://skillshield.io/report/ec92e311479260d2)
Powered by SkillShield