← Home

@cipherstash/protect-ffi-win32-x64-msvc

npm Repository Homepage

Prebuilt binary package for `@cipherstash/protect-ffi` on `win32-x64-msvc`.

17
Versions
ISC
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

cs_lindsaydrew_cipherstashjames-sadlerdan-drapercs-zcjbrewertobyhede

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Change reflects CI/CD provenance adoption, an improvement, for this trusted native-binding package. ai
maintainer-change maintainer-added AI (maintainer-change): Consistent with legitimate org CI/CD transition, not compromise. ai
npm-metadata bundled-binaries AI (npm-metadata): Neon prebuilt binary package; index.node is the intentional deliverable for this platform-specific FFI binding. ai
bogus-package bogus-package AI (bogus-package): Platform-specific binary shim packages structurally lack repo links, keywords, deps, and rich READMEs — all signals are false positives here. ai

Versions (showing 17 of 17)

Version Deps Published
0.29.0 0 / 0
0.28.0 0 / 0
0.27.0 0 / 0
0.26.0 0 / 0
0.25.0 0 / 0
0.24.0 0 / 0
0.23.0 0 / 0
0.22.0 0 / 0
0.21.4 0 / 0
0.21.2 0 / 0
0.21.1 0 / 0
0.21.0 0 / 0
0.20.2 0 / 0
0.20.1 0 / 0
0.20.0 0 / 0
0.19.0 0 / 0
0.18.1 0 / 0

v0.29.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.28.0

2 findings
HIGH Publisher changed: cs-zcjbrewer → GitHub Actions (on 2026-07-08) provenance

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

2 findings
HIGH Publisher changed: cs-zcjbrewer → GitHub Actions (on 2026-07-04) provenance

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

1 finding
LOW No provenance attestation provenance

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

v0.20.2

1 finding
LOW No provenance attestation provenance

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

v0.20.1

1 finding
LOW No provenance attestation provenance

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

v0.20.0

1 finding
LOW No provenance attestation provenance

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

v0.19.0

1 finding
LOW No provenance attestation provenance

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

v0.18.1

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.