w-docx2pdf@1.0.25
A tool for docx2pdf.
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe remote executable is package-aligned with the Windows conversion feature, and the inspected code does not establish malicious intent. The mutable, unchecked binary download creates a concrete supply-chain risk, so this warrants a warning.
Decision evidence
public snapshot- The postinstall hook downloads a Windows executable from a mutable GitHub branch into the package directory.
- The conversion API can download that executable when missing, then launch it to process the requested document.
- The required PDF fixture is binary and the citation tool could not provide a printable source excerpt for it.
- The installer runs only from the installed package directory, and the download URL is the package’s own GitHub repository.
- Executable launch is part of the Windows document-conversion path; no separate malicious behavior was established.
Source & flagged code
8 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.25.
See all versions of w-docx2pdf for other recorded verdicts.
- Review the evidence and your use of w-docx2pdf@1.0.25 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.