T08 · Insecure Dependencies
- Location
SKILL.md:9- Finding
Unpinned Third-Party npm Package Installed as a Global Executable
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:9-18; the global installation command is also documented atSKILL.md:31
Vulnerability Type: Supply-chain exposure through an unpinned third-party dependency
Risk Level: MediumVulnerable Code
yaml "openclaw": { "emoji": "🏛️", "requires": { "bins": ["parliament"] }, "install": [ { "id": "npm", "kind": "node", "package": "@shan8851/parliament-cli", "bins": ["parliament"], "label": "Install parliament-cli (npm)", }, ], },The corresponding setup instruction at line 31 is:
markdown - `npm install -g @shan8851/parliament-cli`Technical Analysis
The Skill requires installation of
@shan8851/parliament-cliwithout pinning an exact version or providing a verified integrity digest. It also directs users to install the package globally. The audited project contains no source code for this dependency, lockfile, package archive, checksum, or provenance evidence that would allow its effective behavior to be reviewed from the project itself.npm packages may execute lifecycle scripts during installation. A mutable package release can also alter the installed
parliamentexecutable after this Skill has been reviewed. Global installation increases exposure by making that executable broadly available in the installing user's environment.This does not prove that the current package is malicious. The vulnerability is the unverified, mutable supply-chain trust boundary created by automatically installing and executing an external package.
Attack Path
- An attacker compromises the npm publisher account, package repository, build pipeline, or another component involved in publishing
@shan8851/parliament-cli. - The attacker publishes a malicious package version under the same package name.
- A user or agent follows the ...[truncated 1258 chars]
- An attacker compromises the npm publisher account, package repository, build pipeline, or another component involved in publishing
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to an exact, reviewed version rather than using a mutable package reference.
- Record and verify the package artifact's cryptographic integrity and trusted publication provenance.
- Include the dependency's auditable source or a reproducible-build reference so its installation and runtime behavior can be independently reviewed.
- Prefer a project-local or isolated installation over
npm install -gto reduce environmental exposure. - Disable npm lifecycle scripts during installation where they are unnecessary, and separately verify that the CLI functions correctly without them.
- Review the selected package version, including its transitive dependencies, lifecycle scripts, executable entry point, network behavior, and release history.
- Use a lockfile or equivalent controlled dependency manifest in an isolated wrapper project and apply automated dependency and provenance checks before upgrades.
- Document a controlled upgrade process requiring security review before changing the pinned version or integrity value.
