T08 · Insecure Dependencies
- Location
package.json:5- Finding
Unpinned and Ecosystem-Inconsistent Third-Party Dependencies
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent Backtrader backtesting skill with ordinary dependency and example-code hygiene risks, not evidence of hidden or malicious behavior.
Install in a dedicated Python virtual environment, prefer pinned requirements or a lockfile, avoid npm install for this package unless the publisher clarifies the JavaScript dependency metadata, and run the example only from a scratch directory where overwriting temp_data.csv would not matter.
package.json:5Unpinned and Ecosystem-Inconsistent Third-Party Dependencies
examples/sma_crossover.py:94Predictable Temporary Filename Permits File Clobbering
The dependency uses a caret version range, which allows newer compatible releases to be installed over time. This creates supply-chain risk because builds may become non-reproducible and could unexpectedly pull in a compromised or vulnerable upstream release.
"version": "1.0.0",
"description": "A skill for building and backtesting quantitative trading strategies using Backtrader.",
"dependencies": {
"backtrader": "^1.9.78.123",
"matplotlib": "^3.0.0"
},
"scripts": {
The matplotlib dependency is specified with a broad caret range, so future installs may resolve to different package versions. That increases exposure to accidental breakage or malicious/vulnerable upstream releases in the software supply chain.
"description": "A skill for building and backtesting quantitative trading strategies using Backtrader.",
"dependencies": {
"backtrader": "^1.9.78.123",
"matplotlib": "^3.0.0"
},
"scripts": {
"test": "python examples/sma_crossover.py"
No suspicious patterns detected.