Is dsh-updater safe to install?
Risk grade: High risk (red) — 4 evidence item(s), basis code. A trust score of 60 may be shown, but it is not a verdict; the grade above is authoritative.
Independent analysis based on public code and declarations. Evidence-based findings; no guarantee of safety.
Evidence
P0 R3_remote_code_exec[README.md:33] tier=3 — curl | bashP1 R4_sensitive_file_exfil[lib/tarball.js:79] tier=1 — .env, accept = ACCEPT_JSON) { const headers = { Accept: accept, 'User-Agent': 'dsh-updater', } const token = env.NPM_TOKEN || env.NODE_AUTH_TOKEN || env.npm_co…P1 R4b_env_config_read[lib/tarball.js:67] tier=1 — process.env) { if (String(name).startsWith('@')) { const scope = String(name).split('/')[0] const scoped = env[`npm_config_${scope}:registry`] if (scoped) retu…P2 R10_no_license[no file:line reference] tier=0 — package has no LICENSE file
Not assessed
- Author identity: UNVERIFIED (no linked GitHub/npm identity)
- Runtime behaviour: NOT executed — a static scan cannot prove what runs.
- Pinned refs, tarballs, local dirs, dependency OSV: NOT assessed.
- Catalog granularity: default branch only.
Freshness
Scan timestamp not reported by the backend — grade freshness cannot be verified. Last seen: 2026-11-22 08:30:01 (not the same as last scanned).