T08 · Insecure Dependencies
- Location
SKILL.md:27- Finding
Unpinned Third-Party Package Installation and Execution
- Content
View full analysis
- Remediation
View remediation
``` 2. Commit an npm lockfile containing registry URLs and integrity hashes. 3. Replace unversioned `npx` use with an explicitly pinned package invocation, for example: ```bash npm exec --package=@agentlink/cli@ -- agentlink init --name "My Assistant" ``` 4. Install dependencies with lockfile enforcement, such as `npm ci`, in supported project workflows. 5. Verify the publisher, package ownership, provenance attestations, signatures, and integrity metadata before installation. 6. Explain and validate why the installed library and executed CLI use different npm scopes. 7. Disable lifecycle scripts where they are unnecessary and operationally compatible, or review all lifecycle scripts before installation. 8. Run the software under a dedicated, least-privileged account or sandbox without unnecessary credentials or filesystem access. 9. Include the audited dependency manifests and lockfile in the project so reviewers can assess the actual dependency graph. ]]>
