@rollup/rollup-linux-x64-musl
Native bindings for Rollup
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 |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Platform-specific native binding; .node binary is the entire purpose of this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Minimal native binding package; no deps/keywords/readme code blocks are expected for this type of package. | ai |
Versions (showing 15 of 115)
| Version | Deps | Published |
|---|---|---|
| 4.22.4 | 0 / 0 | |
| 4.22.3 | 0 / 0 | |
| 4.22.2 | 0 / 0 | |
| 4.22.1 | 0 / 0 | |
| 4.22.0 | 0 / 0 | |
| 4.21.3 | 0 / 0 | |
| 4.21.2 | 0 / 0 | |
| 4.21.1 | 0 / 0 | |
| 4.21.0 | 0 / 0 | |
| 4.20.0 | 0 / 0 | |
| 4.19.2 | 0 / 0 | |
| 4.19.1 | 0 / 0 | |
| 4.19.0 | 0 / 0 | |
| 4.18.1 | 0 / 0 | |
| 4.18.0 | 0 / 0 |
v4.22.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.