T08 · Insecure Dependencies
- Location
references/installation.md:27- Finding
Unpinned Global Dependencies and Unverified Browser Extension
- Content
View full analysis
- Remediation
View remediation
npm install -g @jackwener/opencli@ ``` 2. Publish expected npm integrity hashes, package tarball digests, and Chrome-extension artifact checksums through a trusted channel. Require users to verify them before installation. 3. Record the reviewed package versions and extension release identifier in `SKILL.md` and `references/installation.md`. Do not instruct users to install an unspecified “latest” release. 4. Prefer project-local or isolated installation over global installation. Run the tools in a dedicated container, virtual machine, or restricted operating-system account where practical. 5. Use a dedicated Chrome profile for this Skill. That profile should contain only the Xiaohongshu session required for the workflow and no unrelated accounts, credentials, payment sessions, or sensitive browsing data. 6. Document and review all extension permissions and host access. Restrict the extension to the minimum required domains rather than granting access to all sites. 7. Prefer a verified browser-store release with controlled updates. If Developer Mode installation is necessary, require a fixed signed artifact and checksum verification. 8. Disable npm lifecycle scripts during acquisition where compatible, inspect the package, and only then install or enable the reviewed artifact. 9. Add a controlled update process requiring security review whenever dependency versions, checksums, extension permissions, or release sources change. ]]>
