Summary
Togoder Security scanned the npm package finalhandler@1.2.0 on Oct 4, 2026. An AI review of 1 source file produced 1 low severity finding. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings 1
Informational: Stack Trace Exposure
NPS-DDB2B01DA6A2
In non-production environments, the error handler uses err.stack as the response message. While this aids debugging, it can expose sensitive internal paths or logic if deployed to production without NODE_ENV set to 'production'. However, this is standard behavior for the finalhandler package and not indicative of malicious intent.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| index.js | safe | The code is a legitimate error handling middleware with no malicious patterns; it only contains standard functionality and a minor informational note about stack trace exposure in non-production environments. |
Affected version ranges
None of the 3 scanned versions of finalhandler are flagged high or critical. The latest scanned version, 2.1.1, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 2.1.1 | No issues | 1 | 2.1.1 | |
| 2.1.0 | Not scanned | 1 | 2.1.0 | |
| 1.3.2 | No issues | 1 | 1.3.2 | |
| 1.3.1 | Not scanned | 1 | 1.3.1 | |
| 1.2.0 | No issues | 1 | 1.2.0 | |
| 1.1.2 | Not scanned | 1 | 1.1.2 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of finalhandler
Frequently asked questions
Is finalhandler safe to use?
Our AI source review of finalhandler@1.2.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does finalhandler contain malware?
No malware was identified in finalhandler@1.2.0 when Togoder Security scanned it on Oct 4, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was finalhandler checked?
Togoder Security downloaded the published npm package and had an AI model read its 1 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 finalhandler 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 finalhandler@1.2.0, cost nothing.