@hydranium/data-client-vscode@1.0.0-next.421
VS Code client primitives for the hydranium data-server protocol head; companion of @hydranium/data-server. The extension host relays the data-server's socket to a webview over a vscode-messenger hop, and the webview's data port reads it, so DataConnectio
AI Security Review
scanned 9h ago · by lpm-firewall-aiThe inspected runtime behavior fits a VS Code data-client, but the manifest contains review-directed reassurance about lifecycle safety that appears intended to influence the verdict. I treated that reviewer manipulation as malicious intent.
Decision evidence
public snapshot- The manifest contains unusually persuasive commentary asserting the prepack hook “cannot break the install” and describing the package as safe to publish, which appears aimed at steering security review.
- The declared scripts are build, cleanup, lint, tests, watch, and a prepack guard; no install lifecycle hook is declared.
- The inspected socket code connects to 127.0.0.1 by default, and the messenger code relays notifications between the extension host and its webview.
Source & flagged code
1 flaggedThe manifest contains unusually persuasive commentary asserting the prepack hook “cannot break the install” and describing the package as safe to publish, which appears aimed at steering security review.
package.jsonView on unpkg · L99Findings
Affected versions and remediation
This report applies to @hydranium/data-client-vscode@1.0.0-next.421.
See all versions of @hydranium/data-client-vscode for other recorded verdicts.
- Avoid installing @hydranium/data-client-vscode@1.0.0-next.421. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.