T08 · Insecure Dependencies
- Location
package.json:2- Finding
Unnecessary Runtime Dependency Retrieved Through a Third-Party Package Mirror
- Content
View full analysis
Vulnerability Details
File Location:
package.json:2-4;package-lock.json:8,89-91
Vulnerability Type: Unnecessary third-party dependency and unsafe package source
Risk Level: LowVulnerable Code
package.json:2-4:json "dependencies": { "clawhub": "^0.9.0" }package-lock.json:89-91:json "node_modules/clawhub": { "version": "0.9.0", "resolved": "https://registry.npmmirror.com/clawhub/-/clawhub-0.9.0.tgz",Technical Analysis
The project contains documentation and reference material only. No executable project code uses the
clawhubpackage, and the declared gold-market analysis workflows do not require this runtime dependency. Installing it therefore exceeds the minimum dependency footprint necessary for the Skill's functionality.The lockfile resolves
clawhuband its transitive dependencies throughregistry.npmmirror.com, a third-party mirror rather than the official npm registry. Package integrity hashes provide protection against content differing from the committed lockfile, but they do not remove the need to trust the lockfile itself or the original dependency selection. The semver declaration^0.9.0can also permit later compatible releases when dependency resolution is performed without strictly honoring the existing lockfile.No lifecycle install hook or malicious package code was identified in the audited project files. Consequently, this is a supply-chain exposure rather than evidence that malicious execution currently occurs.
Attack Path
- A user or deployment process runs
npm installor an equivalent dependency installation command. - npm reads the unnecessary
clawhubdependency and its transitive dependency graph. - Package archives are retrieved from the third-party mirror specified by the lockfile.
- If the dependency, a transitive package, the mirror response, or a modified lockfile is compromised, attacker-controlled pa ...[truncated 911 chars]
- A user or deployment process runs
- Remediation
View remediation
Remediation Suggestions
- Remove
clawhubfrompackage.jsonbecause no project code or documented workflow requires it. - Delete and regenerate
package-lock.jsonafter removing the dependency, or remove package metadata entirely if the Skill is documentation-only. - If the package is genuinely required later, document the exact functionality that depends on it and pin a reviewed exact version rather than using a caret range.
- Resolve packages from an organization-approved registry, preferably the official npm registry or a controlled internal proxy.
- Use deterministic installation with
npm ciand retain integrity-protected lockfiles under review. - Disable lifecycle scripts during installation where compatible, such as with
npm ci --ignore-scripts. - Add dependency review, vulnerability scanning, and lockfile-diff checks to the release process.
- Remove
