@oxlint/binding-win32-ia32-msvc
Linter for the JavaScript Oxidation Compiler
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): oxc-project uses GitHub Actions CI/CD for publishing; transition from boshen to GitHub Actions is the documented release process. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Intentional placeholder package; 0.0.0 is the documented stub version for this native binding. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Platform-specific native binding package; .node binary is the intended artifact, built with SLSA provenance. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Platform shard packages intentionally have no deps and minimal READMEs; not spam. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.68.0 | 0 / 0 | |
| 1.67.0 | 0 / 0 | |
| 1.66.0 | 0 / 0 | |
| 1.65.0 | 0 / 0 | |
| 1.64.0 | 0 / 0 | |
| 1.63.0 | 0 / 0 | |
| 1.62.0 | 0 / 0 | |
| 1.61.0 | 0 / 0 | |
| 1.60.0 | 0 / 0 | |
| 1.59.0 | 0 / 0 | |
| 1.58.0 | 0 / 0 | |
| 0.0.0 | 0 / 0 |
v1.68.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.67.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.66.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.65.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.64.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.63.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.61.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.60.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-13. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.59.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-07. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.58.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-31. This could indicate a legitimate maintainer transition or an account compromise.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.