w-docx2pdf@1.0.27
A tool for docx2pdf.
AI Security Review
scanned 13d ago · by lpm-firewall-aiSource confirms an install-time download and later execution of a remote Windows binary, but the inspected code connects both to DOCX-to-PDF conversion and shows no separate attack behavior. The binary artifact could not be verified, so this unresolved executable behavior warrants a warning rather than a clean verdict or a claim of malware.
Decision evidence
public snapshot- The postinstall hook downloads a Windows executable from the package's GitHub repository into a source directory.
- The executable is invoked when the conversion function runs in Microsoft Office mode.
- The executable's contents could not be verified from the required binary artifact, so its behavior remains unresolved.
- The postinstall script returns when the package is not installed under node_modules, limiting its install-time action.
- The download and execution are connected to the package's documented DOCX-to-PDF conversion path.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage ships non-JavaScript build or shell helper files.
srcPython/test.batView on unpkgPackage ships compressed or archive-like blobs.
Findings
Affected versions and remediation
This report applies to w-docx2pdf@1.0.27.
See all versions of w-docx2pdf for other recorded verdicts.
- Review the evidence and your use of w-docx2pdf@1.0.27 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.