← Home

node-red

npm Repository Homepage

Low-code programming for event-driven applications

8
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

knollearydceejay

Keywords

editormessagingiotflow

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require in red.js loads user-supplied settings file — documented, intentional behavior for this package. ai
dependencies unvetted-dep:@node-red/util AI (dependencies): First-party scoped package published alongside node-red at the same version; stable pattern. ai
dependencies unvetted-dep:@node-red/nodes AI (dependencies): First-party scoped package published alongside node-red at the same version; stable pattern. ai
dependencies unvetted-dep:@node-red/runtime AI (dependencies): First-party scoped package published alongside node-red at the same version; stable pattern. ai
dependencies unvetted-dep:@node-red/editor-api AI (dependencies): First-party scoped package published alongside node-red at the same version; stable pattern. ai

Versions (showing 8 of 8)

Version Deps Published
4.1.10 12 / 0
4.1.9 12 / 0
4.1.7 12 / 0
4.1.6 12 / 0
4.1.5 12 / 0
4.1.4 12 / 0
4.1.2 12 / 0
4.1.0 12 / 0

v4.1.10

1 finding
LOW No provenance attestation provenance

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

v4.1.9

1 finding
LOW No provenance attestation provenance

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

v4.1.7

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. Consider requesting the maintainer enable provenance via CI/CD.

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