@rollup/rollup-linux-arm64-gnu MIT 22 versions

@rollup/rollup-linux-arm64-gnu

npm Repository Homepage

Native bindings for Rollup

22

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

shellscaperich_harrisguybedfordlukastaegert

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Rollup migrated to GitHub Actions publishing; SLSA attestation confirms CI/CD origin. Stable for this package.	ai	2026/04/28
npm-metadata	bundled-binaries	AI (npm-metadata): This package's sole purpose is to ship a platform-specific native .node binary for Rollup. The bundled binary is the expected and documented artifact for this package family.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): Platform-specific native binding sub-packages are intentionally minimal: no deps, no keywords, short README. These signals are structural false positives for this package type.	ai	2026/04/23

Versions (showing 22 of 122)

Version	Deps	Published
4.9.0	0 / 0	2023-12-13
4.8.0	0 / 0	2023-12-11
4.7.0	0 / 0	2023-12-08
4.6.1	0 / 0	2023-11-30
4.6.0	0 / 0	2023-11-26
4.5.2	0 / 0	2023-11-24
4.5.1	0 / 0	2023-11-21
4.5.0	0 / 0	2023-11-18
4.4.1	0 / 0	2023-11-14
4.4.0	0 / 0	2023-11-12
4.3.1	0 / 0	2023-11-11
4.3.0	0 / 0	2023-11-03
4.2.0	0 / 0	2023-10-31
4.1.6	0 / 0	2023-10-31
4.1.5	0 / 0	2023-10-28
4.1.4	0 / 0	2023-10-16
4.1.3	0 / 0	2023-10-15
4.1.1	0 / 0	2023-10-15
4.1.0	0 / 0	2023-10-14
4.0.2	0 / 0	2023-10-06
4.0.1	0 / 0	2023-10-06
4.0.0	0 / 0	2023-10-05

v4.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.6.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.5.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.4.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.

v4.3.1

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.

v4.3.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.

v4.2.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.

v4.1.6

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.

v4.1.5

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.

v4.1.4

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.

v4.1.3

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.

v4.1.1

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.

v4.1.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.

v4.0.2

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.

v4.0.1

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.

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