Is gongwen-dsh safe to install?
Risk grade: Watch (yellow) — 3 evidence item(s), basis code. A trust score of 90 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
P1 R4_sensitive_file_exfil[scripts/register.mjs:18] tier=1 — readFileSync(CONFIG_PATH, "utf-8")); } catch { return {}; } } function saveConfig(cfg) { fs.writeFileSync(CONFIG_PATH, JSON.stringify(cfg, null, 2), "utf-8"); …P1 R4b_env_config_read[scripts/register.mjs:18] tier=1 — readFileSync(CONFIG_PATH, "utf-8")); } catch { return {}; } } function saveConfig(cfg) { fs.writeFileSync(CONFIG_PATH, JSON.stringify(cfg, null, 2), "utf-8"); …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-12 20:30:08 (not the same as last scanned).