node — Greenflagged

node

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

aredridel

Keywords

runtime

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): This is a legitimate, long-standing Node.js binary wrapper. Tiny payload and minimal description are by design; isaacs spam flag is a false positive for this established package.	ai	2026/04/24
typosquat	typosquat.levenshtein:zod	AI (typosquat): 'node' is a long-established (~5000 days) Node.js binary wrapper package with no relation to 'zod'; the Levenshtein match is a false positive that generalizes across all versions.	ai	2026/04/24
install-scripts	install-script:preinstall	AI (install-scripts): Preinstall is the documented, stable mechanism for node-bin-gen to select the correct arch-specific Node.js binary. Present across hundreds of versions; not a risk signal for this package.	ai	2026/04/23

Versions (showing 100 of 758)

Version	Deps	Published
26.2.0	1 / 0	2026-05-21
26.1.0	1 / 0	2026-05-08
26.0.0	1 / 0	2026-05-06
25.8.1	1 / 0	2026-03-13
25.8.0	1 / 0	2026-03-04
25.7.0	1 / 0	2026-02-25
25.6.0	1 / 0	2026-02-04
25.5.0	1 / 0	2026-01-27
25.2.1	1 / 0	2025-11-18
25.1.0	1 / 0	2025-10-29
24.16.0	1 / 0	2026-05-22
24.14.1	1 / 0	2026-03-25
24.13.1	1 / 0	2026-02-11
24.13.0	1 / 0	2026-01-14
24.11.1	1 / 0	2025-11-12
24.11.0	1 / 0	2025-10-29
24.9.0	1 / 0	2025-09-26
24.8.0	1 / 0	2025-09-11
24.6.0	1 / 0	2025-08-15
24.4.1	1 / 0	2025-07-16
24.4.0	1 / 0	2025-07-10
24.3.0	1 / 0	2025-06-25
24.2.0	1 / 0	2025-06-10
24.1.0	1 / 0	2025-05-22
24.0.2	1 / 0	2025-05-15
24.0.0	1 / 0	2025-05-07
23.11.1	1 / 0	2025-05-15
23.10.0	1 / 0	2025-03-14
23.6.1	1 / 0	2025-01-22
23.4.0	1 / 0	2024-12-11
23.3.0	1 / 0	2024-11-21
23.1.0	1 / 0	2024-10-25
22.22.3	1 / 0	2026-05-14
22.22.1	1 / 0	2026-03-07
22.22.0	1 / 0	2026-01-14
22.19.0	1 / 0	2025-08-29
22.18.0	1 / 0	2025-08-03
22.17.1	1 / 0	2025-07-16
22.17.0	1 / 0	2025-06-25
22.15.1	1 / 0	2025-05-15
22.15.0	1 / 0	2025-04-24
22.12.0	1 / 0	2024-12-04
22.10.0	1 / 0	2024-10-17
22.5.1	1 / 0	2024-07-20
22.4.1	1 / 0	2024-07-09
22.0.0	1 / 0	2024-04-25
21.7.3	1 / 0	2024-04-11
21.7.2	1 / 0	2024-04-04
21.7.1	1 / 0	2024-03-09
21.7.0	1 / 0	2024-03-07
21.6.2	1 / 0	2024-02-15
21.6.1	1 / 0	2024-01-25
21.6.0	1 / 0	2024-01-22
21.5.0	1 / 0	2024-01-22
21.4.0	1 / 0	2024-01-22
21.3.0	1 / 0	2024-01-22
21.2.0	1 / 0	2023-11-23
21.1.0	1 / 0	2023-10-25
21.0.0	1 / 0	2023-10-17
20.20.2	1 / 0	2026-03-25
20.20.1	1 / 0	2026-03-07
20.20.0	1 / 0	2026-01-14
20.19.5	1 / 0	2025-09-05
20.19.2	1 / 0	2025-05-15
20.18.2	1 / 0	2025-01-22
20.16.0	1 / 0	2024-07-25
20.15.0	1 / 0	2024-06-21
20.12.2	1 / 0	2024-04-11
20.12.1	1 / 0	2024-04-04
20.12.0	1 / 0	2024-03-27
20.11.1	1 / 0	2024-02-15
20.11.0	1 / 0	2024-01-22
20.10.0	1 / 0	2023-11-23
20.9.0	1 / 0	2023-10-25
20.8.1	1 / 0	2023-10-17
20.8.0	1 / 0	2023-10-17
20.7.0	1 / 0	2023-09-26
20.6.1	1 / 0	2023-09-26
20.6.0	1 / 0	2023-09-06
20.5.1	1 / 0	2023-08-22
20.5.0	1 / 0	2023-07-21
20.4.0	1 / 0	2023-07-07
20.3.1	1 / 0	2023-06-25
20.3.0	1 / 0	2023-06-25
20.2.0	1 / 0	2023-05-18
20.1.0	1 / 0	2023-05-04
20.0.0	1 / 0	2023-05-01
19.8.1	1 / 0	2023-03-16
19.8.0	1 / 0	2023-03-16
19.7.0	1 / 0	2023-02-24
19.6.1	1 / 0	2023-02-25
19.6.0	1 / 0	2023-02-03
19.5.0	1 / 0	2023-01-26
19.4.0	1 / 0	2023-01-13
19.3.0	1 / 0	2022-12-15
19.2.0	1 / 0	2022-11-30
19.1.0	1 / 0	2022-11-15
19.0.1	1 / 0	2022-11-05
19.0.0	1 / 0	2022-10-19
18.20.8	1 / 0	2025-03-28

Showing 100 of 758 Next page →

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

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

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

v25.8.1

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.

v25.8.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.

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

v25.6.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.

v25.5.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.

v25.2.1

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.

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

v24.16.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.

v24.14.1

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.

v24.13.1

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.

v24.13.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.

v24.11.1

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.

v24.11.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.

v24.9.0

1 finding

LOW No provenance attestation provenance

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

v24.8.0

1 finding

LOW No provenance attestation provenance

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

v24.6.0

1 finding

LOW No provenance attestation provenance

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

v24.4.1

1 finding

LOW No provenance attestation provenance

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

v24.4.0

1 finding

LOW No provenance attestation provenance

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

v24.3.0

1 finding

LOW No provenance attestation provenance

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

v24.2.0

1 finding

LOW No provenance attestation provenance

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

v24.1.0

1 finding

LOW No provenance attestation provenance

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

v24.0.2

1 finding

LOW No provenance attestation provenance

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

v24.0.0

1 finding

LOW No provenance attestation provenance

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

v23.11.1

1 finding

LOW No provenance attestation provenance

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

v23.10.0

1 finding

LOW No provenance attestation provenance

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

v23.6.1

1 finding

LOW No provenance attestation provenance

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

v23.4.0

1 finding

LOW No provenance attestation provenance

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

v23.3.0

1 finding

LOW No provenance attestation provenance

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

v23.1.0

1 finding

LOW No provenance attestation provenance

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

v22.22.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.

v22.22.1

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.

v22.22.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.

v22.19.0

1 finding

LOW No provenance attestation provenance

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

v22.18.0

1 finding

LOW No provenance attestation provenance

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

v22.17.1

1 finding

LOW No provenance attestation provenance

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

v22.17.0

1 finding

LOW No provenance attestation provenance

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

v22.15.1

1 finding

LOW No provenance attestation provenance

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

v22.15.0

1 finding

LOW No provenance attestation provenance

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

v22.12.0

1 finding

LOW No provenance attestation provenance

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

v22.10.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.

v22.5.1

1 finding

LOW No provenance attestation provenance

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

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

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

v20.20.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.

v20.20.1

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.

v20.20.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.

v20.19.5

1 finding

LOW No provenance attestation provenance

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

v20.19.2

1 finding

LOW No provenance attestation provenance

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

v20.18.2

1 finding

LOW No provenance attestation provenance

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

v20.16.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.

v20.15.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.

v18.20.8

1 finding

LOW No provenance attestation provenance

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