← Home

@mehen/linux-x64-gnu

npm Repository Homepage

Mehen binary for linux-x64

23
Versions
MPL-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

tinovyatkin

Keywords

metricscode-analysiscomplexityrustcli

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata bundled-binaries AI (npm-metadata): Platform binary distribution package; bundled binary is the package's sole purpose, backed by SLSA provenance attestation. ai
bogus-package bogus-package AI (bogus-package): Binary-only sub-package; no deps or elaborate README is expected for this pattern. ai

Versions (showing 23 of 23)

Version Deps Published
1.6.0 0 / 0
1.5.1 0 / 0
1.4.1 0 / 0
1.4.0 0 / 0
1.2.0 0 / 0
1.1.0 0 / 0
1.0.2 0 / 0
0.7.0 0 / 0
0.6.1 0 / 0
0.6.0 0 / 0
0.5.0 0 / 0
0.4.3 0 / 0
0.4.2 0 / 0
0.4.1 0 / 0
0.4.0 0 / 0
0.3.0 0 / 0
0.2.0 0 / 0
0.1.1 0 / 0
0.1.0 0 / 0
0.0.4 0 / 0
0.0.3 0 / 0
0.0.2 0 / 0
0.0.1 0 / 0

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

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

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

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

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

v0.0.3

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

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

INFO Publisher changed: tinovyatkin → GitHub Actions (on 2026-02-15, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (tinovyatkin) on 2026-02-15, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

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