w-docx2pdf@1.0.17
A tool for docx2pdf.
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe source shows a package-aligned conversion workflow, but it also fetches an executable during postinstall and runs it during conversion; the binary’s behavior could not be inspected through the source reader. This supports a warning for unresolved executable risk, not a finding of malicious intent.
Decision evidence
public snapshot- The package runs a postinstall script that downloads a Windows executable from a GitHub URL into the package source directory.
- The converter selects that executable and runs it on Windows when Microsoft Office mode is used.
- The executable supports the package’s stated DOCX-to-PDF purpose and runs only when conversion is invoked on Windows.
- The installer limits the download to installations where the package path includes node_modules.
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.17.
See all versions of w-docx2pdf for other recorded verdicts.
- Review the evidence and your use of w-docx2pdf@1.0.17 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.