← Home

@branchmore/cli-linux-x64

npm Repository Homepage

Linux x64 binary for @branchmore/cli

3
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

asprecic-bmorashu-bmor

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata bundled-binaries AI (npm-metadata): Platform-specific binary distribution package; bundled binary is the package's entire purpose, backed by SLSA provenance. ai
provenance publisher-changed AI (provenance): Publisher changed to GitHub Actions with SLSA attestation, consistent with legitimate CI/CD automation adoption. ai
npm-metadata suspicious-initial-version AI (npm-metadata): 0.0.0 is a common placeholder version for platform-specific binary sub-packages in CLI tool distributions. ai
bogus-package bogus-package AI (bogus-package): Platform binary packages legitimately have no deps, no keywords, and tiny non-JS payloads. ai

Versions (showing 3 of 3)

Version Deps Published
0.2.2 0 / 0
0.2.0 0 / 0
0.0.0 0 / 0

v0.2.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.2.0

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

Package contains compiled binaries that could be backdoors: • bin/bmor

HIGH Publisher changed: asprecic-bmor → GitHub Actions (on 2026-06-09) provenance

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