@neoxr/zapo@1.0.5
TypeScript connector for building WhatsApp Bot (ZapoJS)
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe entrypoint loads extensively obfuscated modules that construct code dynamically, and a source comment attempts to discourage inspection. These facts warrant a warning, but the inspected source does not establish a concrete attack chain.
Decision evidence
public snapshot- The manifest describes a WhatsApp bot connector and names lib/index.js as its entrypoint.
- Importing lib/index.js creates a .cache directory and loads utility, proxy, and runtime modules.
- Several loaded modules construct code with Function from encoded string fragments, leaving their behavior opaque to static inspection.
- A source comment directly tells inspectors to close the inspector.
Source & flagged code
9 flagged · loading sourcePackage declares a runtime dependency whose name matches a Node built-in module.
package.jsonView on unpkgThe manifest describes a WhatsApp bot connector and names lib/index.js as its entrypoint.
package.jsonView on unpkg · L1Findings
Affected versions and remediation
This report applies to @neoxr/zapo@1.0.5.
See all versions of @neoxr/zapo for other recorded verdicts.
- Review the evidence and your use of @neoxr/zapo@1.0.5 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.