ds-01@1.0.6
Make your site best with DS01
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged shell execution is part of the user-invoked component installation flow, and the DS01 token is sent to the configured DS01 API for that service. No install hook, import-time action, or unrelated credential flow was identified.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user explicitly runs a command such as `ds01 add <component>` or `ds01 login`.
Impact
The requested component and its dependencies can modify the user's project. The reviewed source does not show automatic collection or unrelated credential transmission.
Mechanism
The add command authenticates to the configured DS01 API, fetches component files, writes them into the configured project directory, and may install registry-provided dependencies. Login uses browser approval to obtain a DS01 token.
AI rationale
The flagged shell execution is part of the user-invoked component installation flow, and the DS01 token is sent to the configured DS01 API for that service. No install hook, import-time action, or unrelated credential flow was identified.
Evidence
~/.ds01/auth.jsonprocess.cwd()/ds01.config.jsonprocess.cwd()/${componentsPath}/${componentName}/...
Network endpoints2
ds-01.vercel.appDS01_API_URL environment-configured endpoint
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The CLI registers commands and dispatches based on terminal arguments; importing the entry point does not itself run the add action.
- The add command uses the DS01 API by default, with an explicit environment variable override.
- The add command sends its DS01 bearer token, machine ID, timestamp, and device signature to that API.
- Dependency installation occurs inside the add command after component data is fetched.
- Login sends a public device key and machine fingerprint for browser authorization, then saves the returned session token locally.
Evidence against
- The add command installs dependency names returned by the registry through a shell command; this is a meaningful supply-chain risk, though it is part of the explicitly invoked component-install feature.
- The package uses a persistent device key and stores the DS01 token in a local credentials file.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
Source & flagged code
6 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 · L164`;
L65: const { stdout } = await execFileAsync("powershell.exe", [
L66: "-NoProfile",
High
dist/commands/add.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = ds-01@0.1.5
matchedIdentity = npm:ZHMtMDE:0.1.5
similarity = 0.533
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.
Findings
1 Critical5 High2 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/commands/add.js
HighChild Processdist/utils/secureKeyStore.js
HighShelldist/utils/secureKeyStore.js
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.0.6.
See all versions of ds-01 for other recorded verdicts.
- Review the evidence and your use of ds-01@1.0.6 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.