charape@1.0.1
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 postinstall hook performs unrequested project-wide edits and can replace existing Baileys package entrypoints, creating a material dependency redirection risk. Its stated compatibility purpose makes malicious intent unclear, so this warrants a warning rather than a publish block.
Decision evidence
public snapshot- The manifest runs scripts/postinstall.js automatically after installation.
- The hook appends legacy-peer-deps=true to the consumer project’s .npmrc.
- The hook writes proxy package metadata and entrypoints into node_modules/@whiskeysockets/baileys, node_modules/@adiwajshing/baileys, and node_modules/baileys, redirecting those imports to charape.
- The package describes itself as a WhatsApp bot library and the hook labels the proxies as Baileys compatibility bridges.
- The inspected GraphQL code sends supplied credentials to wamo.whatsapp.net; no automatic credential transmission on import was identified.
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.1.
See all versions of charape for other recorded verdicts.
- Review the evidence and your use of charape@1.0.1 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.