T08 · Insecure Dependencies
- Location
README.md:48- Finding
Unpinned Third-Party Package Installation
- Content
View full analysis
Vulnerability Details
File Location:
README.md:48-65; additional occurrences inREADME.md:261-265andSKILL.md:22-24
Vulnerability Type: Supply-chain exposure through unpinned package installation
Risk Level: MediumVulnerable Code
bash # Install langsmith-fetch CLI pip install langsmith-fetchbash npx skills add OthmanAdi/langsmith-fetch-skill --skill langsmith-fetch -gAdditional upgrade instructions amplify the issue:
bash # Reinstall if needed pip install --upgrade langsmith-fetchTechnical Analysis
The installation commands retrieve mutable package versions without pinning a reviewed version or validating an integrity hash. Package-manager installation can execute package-controlled installation logic and subsequently places third-party executable code in the user's environment.
The global
npxinstallation has an expanded scope because it modifies the user's global Agent Skill environment. The automatic upgrade command may replace a previously reviewed package with a newer, compromised release.The dependency itself is necessary for the Skill's declared trace-fetching functionality. However, retrieving the latest available version is not the minimum privilege or trust necessary: the same functionality can be provided using a pinned, verified release.
Attack Path
- An attacker compromises the upstream package, its publishing credentials, a transitive dependency, or the package-resolution path.
- The attacker publishes a malicious version under the package name used by the documentation.
- A user follows
pip install langsmith-fetch,pip install --upgrade langsmith-fetch, or the globalnpxinstallation instruction. - The package manager resolves the mutable dependency to the malicious release.
- Malicious installation or runtime code executes with the permissions of the user running the package manager.
- The code can access file ...[truncated 568 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
langsmith-fetchto a specifically reviewed version rather than installing the latest release. - Use Python hash verification, such as a locked requirements file containing
--hashentries. - Pin the Agent Skill installer and all relevant transitive dependencies.
- Avoid recommending unconditional
--upgradeoperations. - Publish checksums or signatures for approved releases and document how users should verify them.
- Prefer an isolated virtual environment instead of global package installation.
- Document the expected package publisher, source repository, and release checksum so users can detect package substitution.
- Pin
