ds-01@1.1.1
Make your site best with DS01
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package’s own source contains a command-injection risk: registry-provided dependency values are interpolated into a shell command during `ds01 add`. Because this requires an explicit command and there is no evidence of automatic abuse, classify it as a critical vulnerability warning rather than a malicious package block.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs `ds01 add <component>` and the component response contains missing dependency entries.
Impact
A crafted registry dependency value could execute arbitrary shell commands with the user's privileges.
Mechanism
The dependency entries are joined into a string and interpolated into `execSync('npm install ...')` without argument-safe execution or validation.
AI rationale
The package’s own source contains a command-injection risk: registry-provided dependency values are interpolated into a shell command during `ds01 add`. Because this requires an explicit command and there is no evidence of automatic abuse, classify it as a critical vulnerability warning rather than a malicious package block.
Evidence
src/commands/add.tspath.join(cwd, config.componentsPath, componentName)project package.json and npm lock files
Network endpoints1
ds-01.vercel.app
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Critical Vulnerability with medium false-positive risk.
Evidence for warning
- The `add` operation requires an explicit component argument and runs its work in that command’s action.
- The command takes dependency names from the registry response and joins them into a string.
- It passes that string to `execSync` as `npm install ...`, allowing shell metacharacters in registry metadata to become commands.
- The registry URL defaults to `https://ds-01.vercel.app`.
Evidence against
- The manifest has no install lifecycle scripts; its only script is a build command.
- The shell install occurs during the user-requested `add` operation, not automatically at package install or import.
- The add request sends the DS01 token to the DS01 registry endpoint as part of the intended component-fetch flow.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
UrlStrings
Source & flagged code
5 flaggeddist/utils/secureKeyStore.jsView file
1// cli/src/utils/secureKeyStore.ts
L2: import { execFile } from "node:child_process";
L3: import { promisify } from "node:util";
High
Child Process
Package source references child process execution.
dist/utils/secureKeyStore.jsView on unpkg · L1dist/commands/add.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = ds-01@0.1.5
matchedIdentity = npm:ZHMtMDE:0.1.5
similarity = 0.400
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/commands/add.jsView on unpkg5import path from "path";
L6: import { execSync } from "child_process";
L7: import { getToken } from "../utils/config.js";
...
L10: const { machineIdSync } = machineIdPkg;
L11: const API_BASE_URL = process.env.DS01_API_URL || "https://ds-01.vercel.app";
L12: // function for tailwind dependency check
Findings
1 Critical5 High2 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/commands/add.js
HighChild Processdist/utils/secureKeyStore.js
HighShell
HighSame File Env Network Executiondist/commands/add.js
HighRuntime Package Installdist/commands/add.js
HighSemantic Analysis Limiteddist/commands/login.js#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to ds-01@1.1.1.
See all versions of ds-01 for other recorded verdicts.
- Review the evidence and your use of ds-01@1.1.1 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.