← Home

@oxc-transform/binding-darwin-x64

Oxc Transformer Node API

100
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

babeljavascriptjsxoxctransformtransformertsxtypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): oxc-project transitioned to GitHub Actions CI publishing; SLSA attestation confirms legitimate CI/CD origin. ai
npm-metadata bundled-binaries AI (npm-metadata): Native .node binding is the sole purpose of this platform-specific package; stable across all versions. ai
bogus-package bogus-package AI (bogus-package): Platform-specific native binding packages legitimately have no deps and minimal READMEs. ai

Versions (showing 100 of 164)

Version Deps Published
0.140.0 0 / 0
0.139.0 0 / 0
0.138.0 0 / 0
0.137.0 0 / 0
0.136.0 0 / 0
0.135.0 0 / 0
0.134.0 0 / 0
0.133.0 0 / 0
0.132.0 0 / 0
0.131.0 0 / 0
0.130.0 0 / 0
0.129.0 0 / 0
0.128.0 0 / 0
0.127.0 0 / 0
0.126.0 0 / 0
0.125.0 0 / 0
0.124.0 0 / 0
0.123.0 0 / 0
0.121.0 0 / 0
0.120.0 0 / 0
0.119.0 0 / 0
0.118.0 0 / 0
0.117.0 0 / 0
0.116.0 0 / 0
0.115.0 0 / 0
0.114.0 0 / 0
0.112.0 0 / 0
0.111.0 0 / 0
0.110.0 0 / 0
0.109.0 0 / 0
0.108.0 0 / 0
0.107.0 0 / 0
0.106.0 0 / 0
0.105.0 0 / 0
0.104.0 0 / 0
0.103.0 0 / 0
0.102.0 0 / 0
0.101.0 0 / 0
0.99.0 0 / 0
0.98.0 0 / 0
0.97.0 0 / 0
0.96.0 0 / 0
0.95.0 0 / 0
0.94.0 0 / 0
0.93.0 0 / 0
0.92.0 0 / 0
0.91.0 0 / 0
0.90.0 0 / 0
0.89.0 0 / 0
0.88.0 0 / 0
0.87.0 0 / 0
0.86.0 0 / 0
0.85.0 0 / 0
0.84.0 0 / 0
0.83.0 0 / 0
0.82.3 0 / 0
0.82.2 0 / 0
0.82.1 0 / 0
0.82.0 0 / 0
0.81.0 0 / 0
0.80.0 0 / 0
0.79.1 0 / 0
0.79.0 0 / 0
0.78.0 0 / 0
0.77.3 0 / 0
0.77.2 0 / 0
0.77.1 0 / 0
0.77.0 0 / 0
0.76.0 0 / 0
0.75.1 0 / 0
0.75.0 0 / 0
0.74.0 0 / 0
0.73.2 0 / 0
0.73.1 0 / 0
0.73.0 0 / 0
0.72.3 0 / 0
0.72.2 0 / 0
0.72.1 0 / 0
0.72.0 0 / 0
0.71.0 0 / 0
0.70.0 0 / 0
0.69.0 0 / 0
0.68.1 0 / 0
0.68.0 0 / 0
0.67.0 0 / 0
0.66.0 0 / 0
0.65.0 0 / 0
0.64.0 0 / 0
0.63.0 0 / 0
0.62.0 0 / 0
0.61.2 0 / 0
0.61.1 0 / 0
0.61.0 0 / 0
0.60.0 0 / 0
0.59.0 0 / 0
0.58.1 0 / 0
0.58.0 0 / 0
0.57.0 0 / 0
0.56.5 0 / 0
0.56.4 0 / 0
Showing 100 of 164 Next page →

v0.140.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.139.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.138.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.137.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.67.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.

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

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

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

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

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

v0.61.2

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.

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

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

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

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

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

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

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

v0.56.5

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.

v0.56.4

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.