T08 · Insecure Dependencies
- Location
SKILL.md:5- Finding
Unpinned Global Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 5 and 15–17
Vulnerability Type: Unpinned dependencies from mutable upstream sources
Risk Level: MediumComplete Code Snippet
yaml metadata: {"openclaw": {"emoji": "📄", "requires": {"bins": ["mineru-open-api"], "env": ["MINERU_TOKEN"]}, "primaryEnv": "MINERU_TOKEN", "install": [{"id": "npm", "kind": "node", "package": "mineru-open-api", "bins": ["mineru-open-api"], "label": "Install via npm"}, {"id": "go", "kind": "go", "package": "github.com/opendatalab/MinerU-Ecosystem/cli/mineru-open-api", "bins": ["mineru-open-api"], "label": "Install via go install", "os": ["darwin", "linux"]}]}}bash npm install -g mineru-open-api # or via Go (macOS/Linux): go install github.com/opendatalab/MinerU-Ecosystem/cli/mineru-open-api@latestTechnical Analysis
Both documented installation methods resolve mutable dependency versions at installation time. The npm command omits a version and therefore installs whichever release is currently associated with the registry's default distribution tag. The Go command explicitly requests
@latest. Neither command identifies an audited immutable version, commit, checksum, or signature.The npm command also performs a global installation. Depending on the package and package-manager configuration, package lifecycle scripts may run during installation, and package-provided executables are added to the user's command environment. The Go command compiles source resolved from the mutable upstream version selection and installs the resulting executable.
This creates a supply-chain trust boundary that is not fixed by the reviewed Skill. A future compromised or malicious release could differ materially from the version available during this audit. This finding does not establish that the current MinerU package is malicious; it identifies the unsafe dependency-resolution practice.
Attack Path
- An attacker co ...[truncated 1378 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin both installation methods to explicitly reviewed versions rather than relying on implicit latest-version resolution:
bash npm install -g mineru-open-api@<reviewed-version> go install github.com/opendatalab/MinerU-Ecosystem/cli/mineru-open-api@v<reviewed-version> - Update the metadata installation declarations to include the same pinned versions.
- Prefer immutable commit or release references where the package ecosystem supports them.
- Publish expected artifact checksums or signature-verification instructions and require verification before execution.
- Confirm and document the official package publisher, registry, repository, and release-signing identity.
- Avoid global npm installation where practical. Use a project-local dependency, isolated environment, container, or restricted package-manager prefix.
- Review dependency changes before updating the pinned version, including package lifecycle scripts and transitive dependencies.
- Run the CLI with least privilege and expose
MINERU_TOKENonly to the specific process that requires it.
- Pin both installation methods to explicitly reviewed versions rather than relying on implicit latest-version resolution:
