@noob-stupid/dsh-plugin-console@0.5.47
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 manifest has no consumer install hook; its only lifecycle entry checks the package file before publishing. The inspected runtime paths show local route handling, cache-path discovery, and a targeted compatibility patch, with no confirmed attack behavior.
Decision evidence
public snapshot- package.json contains a prepublish-only BOM check and no consumer install hook.
- The flagged framework locations read npm cache configuration and search cache directories for the framework file; they do not show credential collection or transfer.
- The compatibility helper checks for its specific target and existing helper, then backs up the target before applying a targeted rewrite.
- The framework routine records a version and backup timestamp in local state.
- The client calls relative routes; the server exposes them through a loopback route, and the inspected repository route takes its repository value from the request.
- The install diagnosis classifies ignored build-script errors with no automatic retry; the inspected rollback route checks for an existing checkpoint.
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.47.
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.47 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.