Summary
Togoder Security scanned the npm package @actions/core@3.0.0 on Oct 6, 2026. An AI review of 8 source files produced 1 low severity finding. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings 1
process spawning
NPS-9D75ECA1E5C2
The code uses @actions/exec to spawn platform-specific commands (powershell, sw_vers, lsb_release) to retrieve OS information. These are legitimate, non-malicious calls used by the GitHub Actions toolkit to determine the runner platform, and the commands are hardcoded with no external input or obfuscation.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| lib/command.js | safe | No malicious patterns detected; this is the legitimate GitHub Actions toolkit command module that writes formatted workflow commands to stdout. |
| lib/core.js | safe | This is the legitimate @actions/core library from the GitHub Actions toolkit, containing only standard workflow utility functions with no malicious patterns detected. |
| lib/file-command.js | safe | No malicious patterns detected |
| lib/oidc-utils.js | safe | No malicious patterns detected; the code is a standard GitHub Actions OIDC client that securely retrieves and uses short-lived tokens from environment variables. |
| lib/path-utils.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/platform.js | safe | The file is a standard GitHub Actions platform-detection utility that only spawns fixed, non-malicious OS-information commands and contains no exfiltration, credential harvesting, obfuscation, or backdoor behavior. |
| lib/summary.js | safe | No malicious patterns detected; the code is a standard GitHub Actions job summary implementation that reads a path from an environment variable and writes/appends content to it. |
| lib/utils.js | safe | Cleared by Jev triage; no further analysis needed |
Frequently asked questions
Is @actions/core safe to use?
Our AI source review of @actions/core@3.0.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @actions/core contain malware?
No malware was identified in @actions/core@3.0.0 when Togoder Security scanned it on Oct 6, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was @actions/core checked?
Togoder Security downloaded the published npm package and had an AI model read its 8 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.
How do I scan @actions/core together with the rest of my dependencies?
Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in @actions/core@3.0.0, cost nothing.