T08 · Insecure Dependencies
- Location
SKILL.md:116- Finding
Unpinned Third-Party Package Execution with Postinstall Binary Download
- Content
View full analysis
- Remediation
View remediation
``` 2. Document the expected npm integrity digest and require verification against a trusted release manifest before execution. 3. Replace the mutable Git clone workflow with a pinned, reviewed commit or signed tag: ```bash git clone https://github.com/jo-inc/camofox-browser cd camofox-browser git checkout --detach ``` 4. Use a committed lockfile and a deterministic installation command such as `npm ci` rather than an unconstrained `npm install`. 5. Verify the downloaded Camoufox browser artifact using a published cryptographic checksum or signature before installation or execution. 6. Prefer `CAMOFOX_SKIP_DOWNLOAD=true` together with `CAMOUFOX_EXECUTABLE` pointing to a separately obtained and verified browser bundle when practical. 7. Run installation and browser startup as an unprivileged, dedicated user in a sandbox or container with restricted filesystem and network access. Do not run the installation with `sudo` or as root. 8. Disable telemetry for privacy-conservative deployments unless explicitly required: ```bash CAMOFOX_CRASH_REPORT_ENABLED=false ``` 9. If the server is reachable beyond loopback, require `CAMOFOX_ACCESS_KEY`, use TLS through a trusted reverse proxy, and restrict inbound access at the network layer. ]]>
