← Home

@local-docs-mcp/win32-x64

The Windows x64 binary for local-docs-mcp

3
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

peteretelej

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from human publisher to GitHub Actions CI/CD with SLSA attestation is the expected legitimate pattern for this binary distribution package. ai
npm-metadata suspicious-initial-version AI (npm-metadata): 0.0.0 is standard for platform-specific binary stub packages in the optionalDependencies pattern. ai
bogus-package bogus-package AI (bogus-package): No deps and tiny payload are expected for a platform binary stub; not a spam indicator here. ai
npm-metadata bundled-binaries AI (npm-metadata): Platform binary package with SLSA provenance attestation; bundled .exe is the intended artifact, not a backdoor. ai

Versions (showing 3 of 3)

Version Deps Published
0.2.0 0 / 0
0.1.10 0 / 0
0.0.0 0 / 0

v0.2.0

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

Package contains compiled binaries that could be backdoors: • local-docs-mcp.exe

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.

v0.1.10

2 findings
HIGH Publisher changed: peteretelej → GitHub Actions (on 2026-04-13) provenance

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

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.

v0.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.