← Home

@github/copilot-language-server-win32-arm64

Copilot Language Server binary for win32-arm64

4
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

mxie-githubtidy-devcroffzdevm33manuelpuyoljonrohanprimer-cssgraceparkjibrangarciaareliatylerthedevsmocklesimuraikhiga8dustin.greifsrt32githubbotjfuchsandrialexandroujoycezhubteng22dustin.saveryncalteenalaingogaandreiig

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata bundled-binaries AI (npm-metadata): Package's sole purpose is distributing this platform binary; expected every version. ai
maintainer-change maintainer-added AI (maintainer-change): Org-managed CI publishing account transition, consistent across sibling binary packages. ai
bogus-package bogus-package AI (bogus-package): Intentional stub/placeholder package in @github scoped family; sparse metadata is by design for platform-specific stubs. ai

Versions (showing 4 of 4)

Version Deps Published
1.525.0 0 / 0
1.524.0 0 / 0
1.522.0 0 / 0
0.0.1 0 / 0

v1.525.0

2 findings
HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • copilot-language-server.exe

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.524.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.522.0

2 findings
HIGH Publisher changed: bteng22 → GitHub Actions (on 2026-07-16) provenance

This version was published by a different npm account than previous versions on 2026-07-16. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.