← Home

@rolldown/binding-linux-ppc64-gnu

npm Repository Homepage

Fast JavaScript/TypeScript bundler in Rust with Rollup-compatible API.

6
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

broooooklynyyx990803rolldownbotsapphi-red

Keywords

bundleresbuildparcelrolldownrollupwebpack

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Rolldown migrated to GitHub Actions publishing with SLSA attestation; this is a documented CI/CD transition, not a compromise. ai
npm-metadata suspicious-initial-version AI (npm-metadata): Rolldown uses 0.0.0 as a placeholder version for platform-specific binding packages; consistent across the package family. ai
bogus-package bogus-package AI (bogus-package): Platform-specific native binding stub; tiny payload and no deps are expected for an arch-specific .node binary package. ai

Versions (showing 6 of 6)

Version Deps Published
1.1.0 0 / 0
1.0.3 0 / 0
1.0.2 0 / 0
1.0.1 0 / 0
1.0.0 0 / 0
0.0.0 0 / 0

v1.1.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.0.3

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.0.2

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.0.1

2 findings
HIGH Publisher changed: broooooklyn → GitHub Actions (on 2026-05-13) provenance

This version was published by a different npm account than previous versions on 2026-05-13. This could indicate a legitimate maintainer transition or an account compromise.

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.0.0

2 findings
HIGH Publisher changed: broooooklyn → GitHub Actions (on 2026-05-07) provenance

This version was published by a different npm account than previous versions on 2026-05-07. This could indicate a legitimate maintainer transition or an account compromise.

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.0.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.