Action-nodejs-v10

Apache OpenWhisk Docker runtime that runs Node.js v10 actions, giving OpenWhisk users a ready-to-use container to execute JavaScript serverless functions…

  • Development
  • Tools & Utilities
Apache OpenWhisk Docker runtime that runs Node.js v10 actions, giving OpenWhisk users a ready-to-use container to execute JavaScript serverless functions without manual environment setup.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

74/100 Good

Maintained
100last commit 17 days ago
Popular
745,016 GitHub stars
Easy to install
100 install platforms, Docker image
Light to run
No data
Security check
86no serious findings, CI, tests, OpenSSF Scorecard 6.4/10

Based on 4 of 5 factors.

GitHub stars
5,016
Open issues
82
Last commit
2026-11-04
Latest release
v7.1.0
License
MIT
Activity
declining

Checked 16 days ago - source: GitHub (actions/setup-node)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

No first-install notes yet.

Alternatives

No alternatives collected yet.

Common questions

What does Node.js 10 end-of-life mean for an action that depends on it?

Node.js v10 has reached end-of-life, so projects or actions that depend on that version are affected.

Can GitHub Actions' built-in cron be relied on for recurring workloads?

GitHub Actions is not designed for periodical workloads.

Why might a self-hosted runner fail to find Node or nvm?

A self-hosted runner may not find nvm or Node that are already installed in Linux.

Does the Node.js version setting for a project change the action's own runtime?

No, the setting controls which Node.js version your application installs and tests against. It has nothing to do with the runtime the action itself uses.

Answers sourced from byteiota.com, stackoverflow.com, www.reddit.com, www.reddit.com

Community

Collected 48 days ago - public community threads