@noob-stupid/dsh-plugin-console@0.5.46
DSH 框架升级安全与插件升级门控:一键升级、失败自动回滚、升级后回滚上版、旧插件不适配自动禁用;内置多源插件市场为发现层,插件源全部可自定义,可指向公司内网私有源 / 私有索引 / 本地 Git 仓库,纯内网离线可用 | Framework upgrade safety & plugin version gating for DSH, with a customizable multi-source plugin market: point every source at internal mirror
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe inspected runtime hints do not substantiate the scanner’s credential-transfer label, and the framework patch is bounded to the expected DSH parser with a backup. The remaining flagged operations are user-facing plugin management or framework maintenance, with no verified malicious behavior.
Decision evidence
public snapshot- package.json has no install hook; its prepublishOnly script runs a package.json BOM check.
- The runtime hint offsets in framework.js resolve to npm cache configuration, DSH app-boot path lookup, and framework patch calls; they do not show credential transport.
- The state route invokes a narrow app-boot compatibility patch that checks for the expected parser, saves a backup, and records its result.
- Framework upgrade is exposed as a POST route; the upgrade handler processes a requested version.
- The client parses repository package metadata, and the component route clones a repository supplied in the request body.
- Install failure diagnosis assigns ignored build scripts no automatic retry and presents a user-facing hint.
Source & flagged code
7 flaggedPackage source references weak cryptographic algorithms.
lib/server/domain/install-verify.jsView on unpkg · L50Findings
Affected versions and remediation
This report applies to @noob-stupid/dsh-plugin-console@0.5.46.
See all versions of @noob-stupid/dsh-plugin-console for other recorded verdicts.
- Review the evidence and your use of @noob-stupid/dsh-plugin-console@0.5.46 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.