@hydranium/glsp-client-theia@1.0.0-next.378
Theia-coupled client primitives for GLSP heads built on @hydranium/glsp-server. Provides the diagram widget, manager, client contribution and connection-handler bases that Theia-based adopters extend, and binds @hydranium/glsp-client's host-neutral classe
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged client code performs expected GLSP workspace and channel setup, with retries after connection failures. The package entry points and CSS align with its stated Theia diagram client purpose, and the inspected source shows no attack behavior.
Decision evidence
public snapshot- The package entry points expose browser and node APIs; the root entry re-exports the browser surface.
- The client contribution waits for a workspace, then starts and reports a GLSP client connection.
- The connection code listens on the configured GLSP contribution path and manages its channel lifecycle.
- The flagged CSS defines a themed diagram loading overlay.
- No install lifecycle scripts are declared in package.json.
- The inspected client contribution contains no external URL, credential access, process execution, or file access.
- The flagged CSS contains presentation rules only.
Source & flagged code
7 flaggedA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
style/diagram-loading.cssView on unpkgThe flagged CSS defines a themed diagram loading overlay.
style/diagram-loading.cssView on unpkg · L10Findings
Affected versions and remediation
This report applies to @hydranium/glsp-client-theia@1.0.0-next.378.
See all versions of @hydranium/glsp-client-theia for other recorded verdicts.
- Review the evidence and your use of @hydranium/glsp-client-theia@1.0.0-next.378 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.