dsh-win32@0.17.15
Fix and diagnose DeepSeek Harness on native Windows. Official PowerShell, Workspace Write, shortcuts, and legacy preset repair. No WSL.
AI Security Review
scanned 6h ago · by lpm-firewall-aiSetup performs an account change to a publisher-selected repository without recipient-specific consent. This supports blocking based on the verified unrequested account action, even though the npm prepare hook itself only builds the package.
Decision evidence
public snapshot- Running the CLI setup command reaches setup logic.
- Both current and legacy setup paths invoke the star helper without an explicit confirmation step.
- The helper checks for an authenticated GitHub CLI account, then sends a PUT request to star the publisher’s repository.
- The helper writes a local marker containing “yes” before making the account change; that value is not gathered from the user.
- The CI guard skips the action in CI, but ordinary setup has no equivalent consent guard.
- The npm prepare hook runs a build; the account change is tied to CLI setup.
- The request uses GitHub’s CLI and targets the package’s own repository; no credential is copied to another destination.
Source & flagged code
9 flagged · loading sourcePackage source references child process execution.
bin/setup-consent.mjsView on unpkg · L1Source file is highly similar to a previously finalized malicious package; route for source-aware review.
bin/setup-consent.mjsView on unpkgFindings
Affected versions and remediation
This report applies to dsh-win32@0.17.15.
See all versions of dsh-win32 for other recorded verdicts.
- Avoid installing dsh-win32@0.17.15. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.