← Home

@tursodatabase/database-win32-x64-msvc

This is the **x86_64-pc-windows-msvc** binary for `@tursodatabase/database`

6
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

penbergglaubercosta

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions publisher with SLSA attestation is a legitimate CI/CD automation pattern for this package. ai
maintainer-change maintainer-added AI (maintainer-change): Maintainer roster change aligns with org-level transition to automated publishing; no malicious indicators. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of prior maintainer consistent with org transition; SLSA provenance provides integrity assurance. ai
npm-metadata bundled-binaries AI (npm-metadata): Platform-specific native binding package; .node binary is the intended deliverable, not a backdoor. ai
bogus-package bogus-package AI (bogus-package): Platform-specific optional dependency; sparse metadata (no deps, no keywords) is normal for this pattern. ai

Versions (showing 6 of 6)

Version Deps Published
0.6.1 0 / 0
0.6.0 0 / 0
0.5.3 0 / 0
0.5.2 0 / 0
0.1.5 0 / 0
0.1.4 0 / 0

v0.6.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.6.0

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.5.2

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

This version was published by a different npm account than previous versions on 2026-04-01. 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.1.5

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