@noob-stupid/dsh-plugin-console@0.5.102
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 15h ago · by lpm-firewall-aiThe package's lifecycle hook only checks package.json, and the inspected framework upgrade and persistence-related behavior supports the advertised local upgrade console. Upgrade and rollback tasks are request-triggered, and the plugin's route checks restrict access to local requests.
Decision evidence
public snapshot- The only lifecycle script is prepublishOnly, which runs a package.json BOM check.
- The plugin restricts its route to loopback requests and checks the Host header.
- Framework upgrade is registered as a POST route, so its upgrade workflow requires a request.
- The framework patch targets dsh-app-boot's parsePatchList to handle empty array placeholders.
- The upgrade script uses npm registries for the framework installation workflow.
Source & flagged code
19 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.102.
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.102 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.