Summary
Togoder Security scanned the npm package git-log-parser@1.2.1 on Oct 6, 2026. An AI review of 2 source files produced 2 low severity findings. The overall verdict is medium: the findings flag risky but common patterns (dynamic code, unsafe defaults, broad file or network access) rather than confirmed malware.
Findings 2
Spawning processes
NPS-AECAAE95F812
The code spawns the 'git' process with 'log' arguments using child_process.spawn. While this is expected functionality for a git log parser package, spawning processes is a potential red flag that warrants attention. The spawned command is hardcoded to 'git' with 'log' subcommand and concatenated arguments, which could be risky if arguments are not properly sanitized.
Dynamic argument construction
NPS-E40788A6CACE
The args() function constructs command-line arguments from a config object using 'argv-formatter'. This could potentially allow injection of malicious git options or flags if the config object is controlled by an attacker, though the scope is limited to git log formatting options.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| src/index.js | medium | This appears to be a legitimate git log parsing library that spawns git processes to read log data, with no evidence of data exfiltration, credential harvesting, or other malicious behavior. |
| src/fields.js | safe | Cleared by Jev triage; no further analysis needed |
Scanned versions of git-log-parser
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 1.2.1 | Needs review | 2 | Oct 6, 2026 |
Frequently asked questions
Is git-log-parser safe to use?
No confirmed malware was found in git-log-parser@1.2.1, but the review flagged 2 low severity findings for risky patterns worth checking before you rely on it.
Does git-log-parser contain malware?
No malware was identified in git-log-parser@1.2.1 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 git-log-parser checked?
Togoder Security downloaded the published npm package and had an AI model read its 2 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 git-log-parser 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 git-log-parser@1.2.1, cost nothing.