registry / @clawling/clawchat-plugin-openclaw / 2026.9.14-1
@clawling/clawchat-plugin-openclaw@2026.9.14-1
OpenClaw ClawChat channel plugin
Static Scan Results
scanned 2mo ago · by rust-scannerStatic analysis completed at 65.0% confidence. No malicious behavior was detected; 10 low-signal pattern(s) were surfaced and cleared.
Static reason
No blocking static signals were detected.
Decision evidence
public snapshotBehavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
2 flaggeddist/src/plugin-report.jsView file
17try {
L18: const require = createRequire(import.meta.url);
L19: let dir = dirname(fileURLToPath(import.meta.url));
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/src/plugin-report.jsView on unpkg · L17dist/src/liveware-sample.js#virtual:normalized:round1View file
•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 3
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/src/liveware-sample.js#virtual:normalized:round1View on unpkgFindings
1 High4 Medium5 Low
HighSemantic Analysis Limiteddist/src/liveware-sample.js#virtual:normalized:round1
MediumDynamic Requiredist/src/plugin-report.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @clawling/clawchat-plugin-openclaw@2026.9.14-1.
See all versions of @clawling/clawchat-plugin-openclaw for other recorded verdicts.
- Review the evidence and your use of @clawling/clawchat-plugin-openclaw@2026.9.14-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.