T08 · Insecure Dependencies
- Location
SKILL.md:27- Finding
Unpinned Third-Party Package Installation and Execution
- Content
View full analysis
- Remediation
View remediation
``` 2. Require package integrity verification using hashes: ```bash python3 -m pip install --require-hashes -r requirements.txt ``` Maintain a reviewed requirements or lock file containing exact versions and SHA-256 hashes for the package and all transitive dependencies. 3. Link the Skill release to the exact source commit and package artifact that were audited. Prefer reproducible builds and signed release artifacts where available. 4. Install the package in an isolated virtual environment rather than the user's global Python environment: ```bash python3 -m venv .venv .venv/bin/python -m pip install --require-hashes -r requirements.txt ``` 5. Document all filesystem and configuration changes made by `nmem init`. Require explicit user confirmation before modifying `~/.openclaw/mcp.json`, project configuration, or existing memory databases. 6. Provide a non-mutating inspection or dry-run mode for initialization so users can review proposed configuration changes before applying them. 7. Review and constrain optional network-enabled components, including embedding providers, before processing sensitive conversation data. 8. Correct or clarify the installation metadata where the installer entry uses `"kind":"node"` while directing users to install a Python package with `pip`, reducing ambiguity in automated installation behavior. ]]>
