← Home

@oxfmt/binding-darwin-x64

npm Repository Homepage

Formatter for the JavaScript Oxidation Compiler

31
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

boshen

Keywords

formatterjavascriptoxcoxfmtprettiertypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from human publisher (boshen) to GitHub Actions CI/CD is expected for automated binary release pipelines; SLSA attestation confirms integrity. ai
npm-metadata suspicious-initial-version AI (npm-metadata): Platform binding stub; 0.0.0 is a common placeholder version for native binding packages in this pattern. ai
npm-metadata no-description AI (npm-metadata): Native binding stub packages in this ecosystem pattern typically omit descriptions. ai
npm-metadata bundled-binaries AI (npm-metadata): Platform-specific native binding package; .node binary is the intended artifact, published with SLSA provenance. ai
bogus-package bogus-package AI (bogus-package): No-dep, minimal-README pattern is expected for a platform-specific binary sub-package of a monorepo. ai

Versions (showing 31 of 31)

Version Deps Published
0.59.0 0 / 0
0.58.0 0 / 0
0.57.0 0 / 0
0.56.0 0 / 0
0.55.0 0 / 0
0.54.0 0 / 0
0.53.0 0 / 0
0.52.0 0 / 0
0.51.0 0 / 0
0.50.0 0 / 0
0.49.0 0 / 0
0.48.0 0 / 0
0.47.0 0 / 0
0.46.0 0 / 0
0.45.0 0 / 0
0.44.0 0 / 0
0.43.0 0 / 0
0.42.0 0 / 0
0.41.0 0 / 0
0.40.0 0 / 0
0.39.0 0 / 0
0.38.0 0 / 0
0.37.0 0 / 0
0.36.0 0 / 0
0.35.0 0 / 0
0.34.0 0 / 0
0.33.0 0 / 0
0.32.0 0 / 0
0.31.0 0 / 0
0.30.0 0 / 0
0.0.0 0 / 0

v0.59.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.58.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.57.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.42.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.41.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.40.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.39.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.38.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.37.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.36.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.35.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.34.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.33.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.32.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.31.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.30.0

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: boshen → GitHub Actions (on 2026-02-10, 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 (boshen) on 2026-02-10, 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.