@tursodatabase/sync-win32-x64-msvc MIT 16 versions

@tursodatabase/sync-win32-x64-msvc

npm Repository Homepage

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

16

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.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Move to GitHub Actions CI publishing with SLSA attestation is a legitimate, positive transition.	ai	2026/07/10
maintainer-change	maintainer-removed	AI (maintainer-change): Consistent with CI-based publishing migration for official Turso packages.	ai	2026/07/10
npm-metadata	bundled-binaries	AI (npm-metadata): Platform-specific native addon package; .node binary is the intended artifact, backed by SLSA provenance.	ai	2026/04/29
bogus-package	bogus-package	AI (bogus-package): Platform-split packages legitimately lack deps, keywords, and detailed READMEs; pattern is stable across all platform variants.	ai	2026/04/29

Versions (showing 16 of 16)

Version	Deps	Published
0.7.1	0 / 0	2026-07-22
0.7.0	0 / 0	2026-07-13
0.6.1	0 / 0	2026-05-22
0.6.0	0 / 0	2026-05-14
0.5.3	0 / 0	2026-04-02
0.5.2	0 / 0	2026-04-01
0.5.1	0 / 0	2026-03-10
0.5.0	0 / 0	2026-03-04
0.4.4	0 / 0	2026-01-30
0.4.3	0 / 0	2026-01-12
0.4.2	0 / 0	2026-01-07
0.4.1	0 / 0	2026-01-06
0.4.0	0 / 0	2026-01-05
0.3.2	0 / 0	2025-11-02
0.3.1	0 / 0	2025-11-01
0.3.0	0 / 0	2025-10-30

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

2 findings

HIGH Publisher changed: penberg → GitHub Actions (on 2026-03-10) provenance

This version was published by a different npm account than previous versions on 2026-03-10. 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.5.0

2 findings

HIGH Publisher changed: penberg → GitHub Actions (on 2026-03-04) provenance

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

2 findings

HIGH Publisher changed: penberg → GitHub Actions (on 2026-01-30) provenance

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

2 findings

HIGH Publisher changed: penberg → GitHub Actions (on 2026-01-12) provenance

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

2 findings

HIGH Publisher changed: penberg → GitHub Actions (on 2026-01-07) provenance

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

2 findings

HIGH Publisher changed: penberg → GitHub Actions (on 2026-01-06) provenance

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

2 findings

HIGH Publisher changed: penberg → GitHub Actions (on 2026-01-05) provenance

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