slds-lsp-client
A utility package that reports runtime errors to Sentry using @sentry/node.
This report shows the evidence for slds-lsp-client@2026.7.11. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection confirms concrete install-time network collection and telemetry exfiltration of the installer host's public IP to a package-controlled Sentry project. No broader payload or persistence was found, but the lifecycle behavior is sufficient to block.
Decision evidence
public snapshot- package.json preinstall runs `npm install` then `examples/verify.js`.
- examples/verify.js initializes a hard-coded Sentry DSN, resolves public IP, and flushes an error event during install.
- src/index.js defaults Sentry to `sendDefaultPii: true`.
- src/index.js fetches Cloudflare trace endpoints with a browser-like User-Agent and attaches the resolved IP to Sentry.
- Inspected package contains only manifest, README, source, declarations, and verify example.
- No filesystem harvesting, shell execution beyond the declared lifecycle command, eval, dynamic loading, persistence, or AI-agent configuration writes found.
- Runtime reporting APIs require explicit consumer calls; install behavior is confined to the verification script.
Source & flagged code
4 flagged · loading sourceInstall-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkgPackage defines install-time lifecycle scripts.
package.jsonView on unpkgSource file is highly similar to a previously finalized malicious package; route for source-aware review.
src/index.jsFindings
Affected versions and remediation
This report applies to slds-lsp-client@2026.7.11.
The versions list below shows the verdict for each recorded version.
- Avoid installing slds-lsp-client@2026.7.11. 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.