registry / lordceaser-baileys / 3.0.1
lordceaser-baileys@3.0.1
⚠ Under reviewCEASER v3.0.1 - BIG LOGO - 169 files CJS - Pairing FIXED CEASERMD - Pterodactyl FIXED - cache-manager FIXED
Static Scan Results
scanned 10d ago · by rust-scannerStatic analysis completed at 72.0% confidence. No malicious behavior was detected; 11 low-signal pattern(s) were surfaced and cleared.
Static reason
One or more suspicious static signals were detected.
Decision evidence
public snapshotBehavioral surface
ChildProcessCryptoFilesystemNetworkShellWebSocket
HighEntropyStringsMinifiedUrlStrings
NoLicense
Oversized source lightweight scan
WAProto/index.js4.95 MB file, sampled 256 KB
Source & flagged code
4 flaggedpackage.jsonView file
•scripts.postinstall = node -e "try{require('./index.js')}catch(e){}"
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgWAProto/GenerateStatics.shView file
•path = WAProto/GenerateStatics.sh
kind = build_helper
sizeBytes = 301
magicHex = [redacted]
Medium
Ships Build Helper
Package ships non-JavaScript build or shell helper files.
WAProto/GenerateStatics.shView on unpkgWAProto/index.jsView file
•stage = ast_semantic_analysis; reason = ast_path_work_budget_exceeded; limitedFiles = 1
Findings
2 High4 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis LimitedWAProto/index.js
MediumNetwork
MediumShips Build HelperWAProto/GenerateStatics.sh
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to lordceaser-baileys@3.0.1.
See all versions of lordceaser-baileys for other recorded verdicts.
- Review the evidence and your use of lordceaser-baileys@3.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.