@hydranium/glsp-client-theia@1.0.0-next.359
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 nonstandard manifest prose makes categorical claims aimed at preempting review of security-relevant package behavior, which meets the reviewer-manipulation rule. I found no separate runtime attack chain, but the review manipulation itself is evidence of malicious intent.
Decision evidence
public snapshot- package.json contains nonstandard `//...` fields with unusually detailed claims about how reviewers should interpret exports, dependencies, lifecycle behavior, and side effects; one says the prepack guard “cannot break the install it has no business touching.”
- The declared scripts include a `prepack` guard but no install, preinstall, or postinstall hook.
- The package entry points are export barrels that expose browser and node primitives.
- No network, process execution, or filesystem operations were found in the compiled library search.
- The manifest identifies the package as Theia and GLSP client primitives and lists framework dependencies consistent with that purpose.
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 unpkgpackage.json contains nonstandard `//...` fields with unusually detailed claims about how reviewers should interpret exports, dependencies, lifecycle behavior, and side effects; one says the prepack guard “cannot break the install it has no business touching.”
Findings
Affected versions and remediation
This report applies to @hydranium/glsp-client-theia@1.0.0-next.359.
See all versions of @hydranium/glsp-client-theia for other recorded verdicts.
- Avoid installing @hydranium/glsp-client-theia@1.0.0-next.359. 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.