bungoma@1.1.1
AI Security Review
scanned 13d ago · by lpm-firewall-aiInspected source supports a WhatsApp API library with no declared lifecycle scripts. The scanner’s secret and eval signals correspond to protocol constants and an optional audio decoder import; no malicious behavior was confirmed.
Decision evidence
public snapshot- package.json identifies bungoma as a WhatsApp Web API library and declares lib/index.js as its entry point.
- package.json ends after its dependency list without declaring lifecycle scripts.
- lib/WABinary/constants.js contains protocol token strings and WhatsApp OTP URL constants, consistent with protocol data rather than a credential secret.
- lib/Utils/rich-messages.js builds WhatsApp message context metadata from quoted-message fields.
- lib/Utils/messages-media.js uses eval only to dynamically import the audio-decode module for waveform processing.
- Video thumbnail generation invokes ffmpeg with a file path and generated temporary image filename.
Source & flagged code
7 flagged · loading sourcePackage contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L603Google API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L603Package source references a known benign dynamic code generation pattern.
lib/Utils/messages-media.jsView on unpkg · L256Findings
Affected versions and remediation
This report applies to bungoma@1.1.1.
See all versions of bungoma for other recorded verdicts.
- Review the evidence and your use of bungoma@1.1.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.