charape@1.0.0
Enterprise-grade WhatsApp Web Baileys library and multi-bot runner supervisor with session crash guard.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe automatic postinstall hook can replace entry files in existing Baileys packages in the consumer’s project and redirect their imports to charape. This is an install-time modification of unrelated packages, so the package should be blocked.
Decision evidence
public snapshot- The package runs scripts/postinstall.js automatically during installation.
- The hook targets three Baileys package paths under the consumer’s node_modules and skips only a target that resolves to charape’s own package root.
- For each target, the hook writes a proxy package.json and proxy entry files, which can replace files in an existing Baileys package without checking whether it is already installed.
- The hook’s comments describe the proxies as compatibility bridges for Baileys package names.
Source & flagged code
10 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L600Findings
Affected versions and remediation
This report applies to charape@1.0.0.
See all versions of charape for other recorded verdicts.
- Avoid installing charape@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.