w-docx2pdf@1.0.28
A tool for docx2pdf.
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe automatic install hook fetches a native executable, and package code later launches it for a conversion request. The host is package-aligned and the launch is user-invoked, but the required binary fixture could not be resolved from source inspection; this supports a warning for an unresolved staged executable carrier, not a block.
Decision evidence
public snapshot- The package runs a postinstall script that downloads an executable from a GitHub URL into the package source directory.
- The downloaded executable is later launched during Microsoft Office conversion when the caller invokes the conversion API.
- The required PDF fixture is binary and could not be resolved through source inspection, so a clean verdict is not supported.
- The inspected download host is the package's GitHub repository, and the executable launch is tied to a conversion request.
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.28.
See all versions of w-docx2pdf for other recorded verdicts.
- Review the evidence and your use of w-docx2pdf@1.0.28 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.