← Home

@simlin/mcp-win32-x64

Platform binary for @simlin/mcp (win32-x64)

5
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

bpowers

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): 0.0.0 is intentional for platform binary stubs; consistent with the optionalDependencies pattern. ai
bogus-package bogus-package AI (bogus-package): Platform binary stub packages legitimately have no deps, no keywords, and tiny payloads. ai
npm-metadata bundled-binaries AI (npm-metadata): Platform binary package by design; SLSA provenance attestation confirms CI/CD build integrity. ai

Versions (showing 5 of 5)

Version Deps Published
0.1.6 0 / 0
0.1.4 0 / 0
0.1.2 0 / 0
0.1.1 0 / 0
0.0.0 0 / 0

v0.1.6

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

Package contains compiled binaries that could be backdoors: • bin/simlin-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.4

1 finding
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.2

1 finding
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.1

1 finding
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.