T08 · Insecure Dependencies
- Location
SKILL.md:23- Finding
Execution of an Unpinned Third-Party Package
- Content
View full analysis
- Remediation
View remediation
market compass ``` 2. Verify the selected release before documenting it: - Confirm the expected package publisher and registry. - Review the package entry point and lifecycle scripts. - Audit direct and transitive dependencies. - Record the approved package version in the repository. 3. Enforce package integrity: - Use a lockfile that records exact transitive versions and integrity hashes. - Install with a reproducible, frozen-lockfile workflow. - Prefer an internally mirrored or allowlisted registry containing reviewed artifacts. 4. Avoid runtime package retrieval where feasible: - Vendor or package a reviewed client with the Skill. - Alternatively, require administrators to install an approved version in advance and verify its version before execution. 5. Reduce execution exposure: - Run the client in a sandbox with minimal filesystem and network access. - Provide only the API credential needed for this operation. - Do not expose unrelated environment variables, credentials, or user files. - Restrict outbound network access to the required API and approved package infrastructure. 6. Add operational verification: - Check the installed package version against an explicit allowlist before invocation. - Fail closed if the version or integrity value differs from the reviewed artifact. - Periodically review dependency advisories and deliberately update the pinned version after security assessment. ]]>
