@hydranium/glsp-client-theia@1.0.0-next.358
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 6d ago · by lpm-firewall-aiThe runtime evidence reviewed is consistent with a Theia GLSP client, but package.json contains misleading, review-oriented framing about exports and lifecycle behavior. Under the reviewer-manipulation rule, that is evidence of malicious intent.
Decision evidence
public snapshot- package.json contains lengthy extra fields that frame the stylesheet export as safe and claim it cannot affect reachability automatically.
- A second extra field says the prepack hook “has no business touching” installation, steering interpretation toward a benign verdict.
- These review-oriented claims are embedded in package metadata and include misleading framing about the package’s export behavior.
- No preinstall, install, or postinstall lifecycle hook is declared.
- The prepack script checks that expected build output exists before packing.
- The browser widget imports the package’s stylesheet for its loading overlay.
Source & flagged code
3 flaggedA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
style/diagram-loading.cssView on unpkgpackage.json contains lengthy extra fields that frame the stylesheet export as safe and claim it cannot affect reachability automatically.
package.jsonView on unpkg · L101Findings
Affected versions and remediation
This report applies to @hydranium/glsp-client-theia@1.0.0-next.358.
See all versions of @hydranium/glsp-client-theia for other recorded verdicts.
- Avoid installing @hydranium/glsp-client-theia@1.0.0-next.358. 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.