Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 19:06 UTC

node-red / node-red-nodes

Extra nodes for Node-RED

JavaScript · HTMLCustom license★ 1,087 stars⑂ 612 forkssince Sep 2013View on GitHub ↗

node-red/node-red-nodes holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Vitality (68/100) and lowest on AI Readiness (39/100). It was last updated 4 days ago. 2 contributors account for most of its recent work.

65
overall / 100
Good

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

65
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 60 is calibrated to 65 on the published index scale (record calibration 2026-08-02).

Ownership

Node-REDOrganization
3,098 followers38 public repossince Sep 2013

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmnode-red-nodes0.1.013022546 days agonode-rednodesflow

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

68Good · 21% of overall
How it's scored
36/36Push recency — last push 4 days ago
17.3/36Commit cadence — 25/52 weeks with commits
15.9/18Commit volume — 58 commits in the last year
10/10OpenSSF Scorecard: Maintained — 11 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year58
human_commit_share0.97
days_since_last_push4
active_weeks_last_year25
How it's scored
27/27Ships releases — 6 releases published
0/36Release recency — latest release 4,463 days ago
19.8/27Release cadence — a release every ~47.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count6
latest_release_tag0.8.0
releases_from_tagsno
days_since_latest_release4,463
mean_days_between_releases47.4
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

66Good · 17% of overall
How it's scored
49.2/60Stars — 1,087 stars
23.2/25Forks — 612 forks
9.8/15Watchers — 60 watchers
Inputs used
forks612
stars1,087
watchers60
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes
How it's scored
28.2/80Monthly downloads — 130 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesnode-red-nodes
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads130
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

67Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
13.5/22.5Commit distribution — top contributor authored 40% of commits
13.5/13.5Contributor breadth — 99 contributors
10/10OpenSSF Scorecard: Contributors — project has 16 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled99
top_contributor_share0.398
How it's scored
32.8/42Issue resolution — 78% of issues closed
21.8/30PR acceptance — 330/454 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 5/27 approved changesets -- score normalized to 1
Inputs used
merged_prs330
open_issues146
closed_issues520
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.781
closed_unmerged_prs124
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
25/25Owner reach — 3,098 followers of node-red
23.6/25Track record — 38 public repos, account ~13 yr old
Inputs used
followers3,098
owner_typeOrganization
is_verifiedno
owner_loginnode-red
public_repos38
account_age_days4,759
How it's scored
25/25Published & resolvable — 1 package(s) on npm
4/35Publish recency — latest publish 2,546 days ago
12/20Version history — 2 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesnode-red-nodes
ecosystemsnpm
any_deprecatedno
min_days_since_publish2,546

Engineering Quality

Are baseline engineering and documentation practices in place?

44Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 8 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — http://nodered.org
10/10Repository description
10/10Topics — 2 topics
10/10Wiki
Inputs used
topicshacktoberfest, node-red
has_wikiyes
homepage—
docs_sitehttp://nodered.org
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

60Moderate · 16% of overall
How it's scored
6.8/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 0 out of 8 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 5/27 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 16 contributing companies or organizations
0/10Dangerous-Workflow — no data
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 11 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate5
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages48
unassessed_packages46
affected_by_severitymoderate 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 48 resolved dependencies against OSV. 46 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

39Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
9.3/40Legible commit history — 17 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.175
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 3 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.03
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
54.6/55Manageable file sizes — 1/127 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes71,438
source_files_sampled127
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

1,087GitHub stars
99contributors
58commits, last 12 months
4days since last push
6releases
2bus factor
146open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 612 ⇿
0Stars
612Forks
6Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

012525037550062560282013-092020-032026-09
Major 0Minor 6Patch 0

Each point covers 12 days.

OpenSSF Scorecard 5.0 / 10
5.0aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-14 19:06 UTC

9Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 8 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 5/27 approved changesets -- score normalized to 1
10Contributorsproject has 16 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained11 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmjshint2.13.6package.json
npmjshint-stylish2.2.1package.json
All dependencies 94

Full resolved dependency set from the GitHub dependency graph: 2 direct and 92 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npmjshint2.13.6direct
npmjshint-stylish2.2.1direct
npm@abandonware/eddystone-beacon-scanner3.0.1-2indirect
npm@rowanmanning/feed-parser2.1.3indirect
npm@toon-format/toon^4.1.1indirect
npm@xmpp/client^0.14.0indirect
npmbadwords^1.0.0indirect
npmblinkstick1.2.0indirect
npmbody-parser^1.20.3indirect
npmcbor-x^1.6.0indirect
npmdummy-json3.0.5indirect
npmeddystone-beaconnatcl/node-eddystone-beaconindirect
npmexif0.6.0indirect
npmexifreader4.41.0indirect
npmfeedparser2.3.1indirect
npmgeo.what3words^2.0.0indirect
npmgrunt1.6.1indirect
npmgrunt-cli1.4.3indirect
npmgrunt-contrib-jshint3.2.0indirect
npmgrunt-jscs3.0.1indirect
npmgrunt-lint-inline1.0.0indirect
npmgrunt-simple-mocha0.4.1indirect
npmheatmiser~2.0.0indirect
npmhidstream2.1.0indirect
npmimap0.8.19indirect
npmip^2.0.1indirect
npmirc^0.5.2indirect
npmlevel^6.0.0indirect
npmmailparser3.9.14indirect
npmmailparser3.9.9indirect
npmmarkdown-it14.3.0indirect
npmmarkdown-it^14.3.0indirect
npmmcp-spi-adc^3.2.0indirect
npmmdns^2.5.1indirect
npmmocha6.2.3indirect
npmmongodb^3.6.3indirect
npmmqlight1.0.xindirect
npmmsgpack-lite0.1.26indirect
npmmsgpack-lite^0.1.26indirect
npmmultilang-sentiment1.2.0indirect
npmmultilang-sentiment^2.0.0indirect
npmmysql23.23.0indirect
npmnet-snmp^3.26.0indirect
npmngeohash0.6.3indirect
npmngeohash^0.6.3indirect
npmnma0.2.2indirect
npmnode-blink10.5.1indirect
npmnode-dweetio0.0.11indirect
npmnode-hid0.4.*indirect
npmnode-notifier^10.0.1indirect
npmnode-pid-controller0.0.3indirect
npmnode-pop30.11.0indirect
npmnode-prowl0.1.8indirect
npmnode-red4.1.8indirect
npmnode-red-node-test-helper0.3.2indirect
npmnode-ssdp^3.3.0indirect
npmnodemailer9.1.1indirect
npmoctalbonescript^1.2.2indirect
npmpngjs2.3.1indirect
npmproxyquire2.1.3indirect
npmpureimage^0.4.18indirect
npmpushbullet3.0.0indirect
npmpushbullet^2.4.0indirect
npmpusher^5.1.2indirect
npmpusher-js^8.0.1indirect
npmpushover-notifications^1.2.3indirect
npmq^1.5.1indirect
npmredis0.12.1indirect
npmrequest^2.88.0indirect
npmrequest^2.88.2indirect
npmsemver5.7.2indirect
npmsensortag~1.3.0indirect
npmsentiment2.1.0indirect
npmserialport^12.0.0indirect
npmshould13.2.3indirect
npmsinon7.5.0indirect
npmsmtp-server3.18.5indirect
npmsmtp-server3.19.2indirect
npmspacetime^7.4.3indirect
npmsqlite3^6.0.1indirect
npmstomp-client^0.9.0indirect
npmsuncalc^1.9.0indirect
npmsupertest4.0.2indirect
npmtail^2.2.6indirect
npmtwilio^3.11.3indirect
npmtwitter-ng0.6.2indirect
npmurl^0.11.4indirect
npmutil^0.12.5indirect
npmwake_on_lan^1.0.0indirect
npmwhen3.7.8indirect
npmwhen^3.7.8indirect
npmwordpos0.1.*indirect
npmws~6.2.1indirect
npmxml2js^0.4.23indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 48 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct. 46 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
mysql23.23.0indirectmoderate13.23.1

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.