← Home

@suprsend/cli-win32-arm64

npm Repository Homepage

SuprSend CLI binary for win32-arm64. Installed automatically by the `suprsend` package.

4
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

sivaram004gauravsuprsendanirudh.aswal

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-specific placeholder packages in this family. ai
npm-metadata bundled-binaries AI (npm-metadata): Platform-specific CLI binary distribution package; .exe is the intended artifact, backed by SLSA provenance attestation. ai
bogus-package bogus-package AI (bogus-package): Stub/platform-split package pattern; no deps, minimal README, and no keywords are expected for this type of package. ai

Versions (showing 4 of 4)

Version Deps Published
1.0.0 0 / 0
0.2.24 0 / 0
0.2.23 0 / 0
0.0.0 0 / 0

v1.0.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.2.24

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

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

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

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