← Home

@vybestack/llxprt-code-lsp

LLxprt Code LSP service

5
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

acoliver

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:zod AI (phantom-deps): Zod is a legitimate runtime dependency for LSP service validation; indirect usage through framework is normal. ai
phantom-deps phantom-dep:vscode-jsonrpc AI (phantom-deps): vscode-jsonrpc is core LSP infrastructure; indirect usage through LSP framework is expected. ai
phantom-deps phantom-dep:@modelcontextprotocol/sdk AI (phantom-deps): MCP SDK is the primary LSP framework; indirect usage through wrapper is normal for this package type. ai
phantom-deps phantom-dep:typescript-language-server AI (phantom-deps): typescript-language-server is the wrapped LSP server; indirect delegation is the intended usage pattern. ai

Versions (showing 5 of 5)

Version Deps Published
0.10.0 4 / 3
0.9.3 4 / 2
0.9.2 4 / 2
0.9.1 4 / 2
0.9.0 4 / 2

v0.10.0

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: acoliver → GitHub Actions (on 2026-07-25, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (acoliver) on 2026-07-25, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.