@oxlint/binding-linux-ppc64-gnu MIT 33 versions

@oxlint/binding-linux-ppc64-gnu

npm Repository Homepage

Linter for the JavaScript Oxidation Compiler

33

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

eslintjavascriptlinteroxcoxlinttypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Transition from manual (boshen) to GitHub Actions publishing is confirmed by SLSA provenance attestation; expected for this project.	ai	2026/05/10
npm-metadata	suspicious-initial-version	AI (npm-metadata): Intentional placeholder package for a platform binding; 0.0.0 is expected for this stub.	ai	2026/05/04
npm-metadata	bundled-binaries	AI (npm-metadata): Platform-specific native binding package; .node binary is the intended artifact, published with SLSA provenance.	ai	2026/04/29
bogus-package	bogus-package	AI (bogus-package): Binary shard packages legitimately have no deps and minimal READMEs; this is a standard pattern for optional platform packages.	ai	2026/04/29

Versions (showing 33 of 33)

Version	Deps	Published
1.75.0	0 / 0	2026-07-21
1.74.0	0 / 0	2026-07-14
1.73.0	0 / 0	2026-07-06
1.72.0	0 / 0	2026-06-29
1.71.0	0 / 0	2026-06-22
1.70.0	0 / 0	2026-06-15
1.69.0	0 / 0	2026-06-08
1.68.0	0 / 0	2026-06-01
1.67.0	0 / 0	2026-05-26
1.66.0	0 / 0	2026-05-19
1.65.0	0 / 0	2026-05-15
1.64.0	0 / 0	2026-05-11
1.63.0	0 / 0	2026-05-05
1.62.0	0 / 0	2026-04-27
1.61.0	0 / 0	2026-04-20
1.60.0	0 / 0	2026-04-13
1.59.0	0 / 0	2026-04-07
1.58.0	0 / 0	2026-03-31
1.57.0	0 / 0	2026-03-24
1.56.0	0 / 0	2026-03-16
1.55.0	0 / 0	2026-03-12
1.54.0	0 / 0	2026-03-12
1.53.0	0 / 0	2026-03-11
1.52.0	0 / 0	2026-03-10
1.51.0	0 / 0	2026-03-02
1.50.0	0 / 0	2026-02-23
1.49.0	0 / 0	2026-02-19
1.48.0	0 / 0	2026-02-16
1.47.0	0 / 0	2026-02-12
1.46.0	0 / 0	2026-02-10
1.45.0	0 / 0	2026-02-10
1.44.0	0 / 0	2026-02-10
0.0.0	0 / 0	2026-02-02

v1.75.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.74.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.73.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.72.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.71.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.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.

v1.56.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.55.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.54.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.53.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.52.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.51.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.50.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.49.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.48.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.47.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.46.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.45.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.44.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.