@oxc-resolver/binding-linux-ppc64-gnu
Oxc Resolver Node API
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Platform-shard packages legitimately have no deps, sparse READMEs, and inherit semver from the parent package family. | ai | |
| — | bundled-binaries | platform-specific prebuilt oxc-resolver native binding from @boshen (HIGH trust); bundled native binary is the package's intended purpose | sean |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 11.19.1 | 0 / 0 | |
| 11.19.0 | 0 / 0 | |
| 11.18.0 | 0 / 0 | |
| 11.17.1 | 0 / 0 | |
| 11.17.0 | 0 / 0 | |
| 11.16.4 | 0 / 0 | |
| 11.16.3 | 0 / 0 | |
| 11.16.2 | 0 / 0 | |
| 11.16.1 | 0 / 0 | |
| 11.16.0 | 0 / 0 | |
| 11.15.0 | 0 / 0 | |
| 11.14.2 | 0 / 0 | |
| 11.14.0 | 0 / 0 | |
| 11.13.2 | 0 / 0 | |
| 11.13.1 | 0 / 0 | |
| 11.13.0 | 0 / 0 | |
| 11.12.0 | 0 / 0 | |
| 11.11.1 | 0 / 0 | |
| 11.11.0 | 0 / 0 | |
| 11.10.0 | 0 / 0 | |
| 11.9.0 | 0 / 0 | |
| 11.8.4 | 0 / 0 | |
| 11.8.3 | 0 / 0 | |
| 11.8.2 | 0 / 0 | |
| 11.8.0 | 0 / 0 | |
| 11.7.2 | 0 / 0 | |
| 11.7.1 | 0 / 0 | |
| 11.6.2 | 0 / 0 | |
| 11.6.1 | 0 / 0 | |
| 11.6.0 | 0 / 0 | |
| 11.5.2 | 0 / 0 |
v11.19.1
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.19.0
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.18.0
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.17.1
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.17.0
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.16.4
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.16.3
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.16.2
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.16.1
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.16.0
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.15.0
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.14.2
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.14.0
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.13.2
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.13.1
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.13.0
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.12.0
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.11.1
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.11.0
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.10.0
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.9.0
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.8.4
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.8.3
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.8.2
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.8.0
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.7.2
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.7.1
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.6.2
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.6.1
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.6.0
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.5.2
2 findingsPackage contains compiled binaries that could be backdoors: • resolver.linux-ppc64-gnu.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.