@hydranium/glsp-client-theia@1.0.0-next.376
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 contribution handles GLSP channel connections and retries, and the package declares no install lifecycle hook. The source does not substantiate the scanner's fingerprint alert as malicious behavior.
Decision evidence
public snapshot- The package exports browser and node integration entry points for its stated Theia GLSP purpose.
- Its scripts contain build, cleanup, lint, test and prepack tasks; no install lifecycle hook is declared.
- The flagged client code creates a GLSP connection and handles connection closure as a client lifecycle event.
- The connection listener uses the GLSP contribution path and resolves the waiting channel; no unrelated host or collector appears in this flow.
- The README describes the client as waiting for a workspace and restarting after failed starts or lost connections.
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 unpkgSource fingerprint signature matches a known malicious package signature; route for source-aware review.
lib/browser/client-contribution.jsView on unpkgFindings
Affected versions and remediation
This report applies to @hydranium/glsp-client-theia@1.0.0-next.376.
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.376 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.