@hydranium/glsp-client-theia@1.0.0-next.379
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 executable behavior inspected appears consistent with a Theia GLSP client, but the manifest includes reviewer-oriented commentary that attempts to steer interpretation of package behavior. Under the review rules, package text that manipulates the review is evidence of malicious intent.
Decision evidence
public snapshot- The manifest contains unusually reviewer-oriented commentary that preemptively frames package behavior and argues that apparent export and dependency issues are harmless.
- The client contribution waits for a workspace and establishes its GLSP client connection as part of its lifecycle.
- The manifest declares no install, preinstall, or postinstall hooks; its scripts are build, lint, test, cleanup, and prepack tasks.
- The inspected client code manages GLSP channels and client restarts; no credential collection, subprocess execution, or unrelated network destination was identified.
Source & flagged code
5 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.379.
See all versions of @hydranium/glsp-client-theia for other recorded verdicts.
- Avoid installing @hydranium/glsp-client-theia@1.0.0-next.379. 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.