T08 · Insecure Dependencies
- Location
SKILL.md:28- Finding
Unpinned Third-Party Package Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:28-31; additional occurrences inREADME.md:34-36andREADME.md:60-62
Vulnerability Type: Supply-chain exposure through unpinned package installation
Risk Level: MediumVulnerable Code
SKILL.md:28-31:markdown Or pip install if published: ```bash pip install feelings-frameworktext `README.md:34-36`: ```markdown ```bash pip install feelings-frameworktext `README.md:60-62`: ```markdown ```bash npm install feelings-frameworktext ### Technical Analysis The documentation instructs users to install `feelings-framework` by package name without pinning an exact version or verifying the retrieved artifact with a hash, signature, lockfile, or trusted publisher identity. These commands resolve mutable content from the package registry configured in the user's environment. Consequently, the installed package is not guaranteed to correspond to the local source code reviewed in this audit. The wording “if published” in `SKILL.md` also leaves the ownership and expected identity of the registry package unclear. This creates a supply-chain risk if the package name is unclaimed, transferred, compromised, shadowed through dependency confusion, or updated with malicious content. Package installation or subsequent import can then execute code that is absent from the audited project. ### Attack Path 1. An attacker gains control of the relevant Python or npm package name, compromises its publisher account, or influences package resolution through a malicious registry configuration. 2. The attacker publishes a package version containing malicious installation, build, import-time, or runtime code. 3. A user follows the documented `pip install feelings-framework` or `npm install feelings-framework` command. 4. The package manager resolves and installs the attacker-controlled or compromised artifact because no version or integ ...[truncated 1024 chars]- Remediation
View remediation
Remediation Suggestions
-
Prefer installation from the bundled, reviewed source rather than an external registry:
bash python -m pip install .For development use:
bash python -m pip install -e . -
If registry installation is required, pin an exact reviewed version:
bash python -m pip install feelings-framework==1.0.0 npm install feelings-framework@1.0.0 --save-exact -
For Python distribution, publish and document cryptographic hashes and install with a hash-enforced requirements file:
text feelings-framework==1.0.0 --hash=sha256:<verified-digest>bash python -m pip install --require-hashes -r requirements.txt -
Commit appropriate lockfiles for consumers or examples and use reproducible installation workflows such as
npm ci. -
Explicitly document the authoritative registry, expected publisher or organization, package URL, source repository, and release verification procedure.
-
Protect publisher accounts with multi-factor authentication and trusted publishing, and verify that built registry artifacts correspond to tagged source releases.
-
Remove the external installation instructions until package ownership and artifact provenance have been confirmed.
-
