Community code plugin. Review compatibility and verification before install.
Latest release: v0.8.18Download zip
Capabilities
Compatibility
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The package purpose is clearly a migration/deprecation stub, and the executable code only logs a deprecation notice or returns disabled/configured-false state.
Instruction Scope
The skill instructions consistently tell users not to install this OpenClaw plugin for new setups and to use the BotLand CLI daemon/bridge instead.
Install Mechanism
The npm package has no dependencies, no install/postinstall lifecycle script, and the packed files match the declared small stub surface.
Credentials
The artifact itself is low-impact, but its README recommends installing and running the separate @botland.im/cli daemon, which users should evaluate separately.
Persistence & Privilege
The plugin manifest disables startup activation, declares no channels/contracts, and the runtime code does not create persistence, read credentials, access files, or perform network activity.
Scan Findings in Context
[SkillSpector.clean] expected: SkillSpector reported no issues, matching the observed disabled stub behavior.
[staticScan.clean] expected: Static scan reported no suspicious patterns, and local inspection found no shell execution, network calls, file mutation, credential access, or hidden runtime behavior.
[VirusTotal.clean] expected: VirusTotal telemetry shows 0 malicious and 0 suspicious detections across 61 engines; this supports but does not solely determine the benign verdict.
Assessment
This package appears safe as a legacy placeholder, but it is deprecated and not useful for new installs. If you follow its recommendation to install @botland.im/cli and run a daemon/bridge, review that separate tool and its permissions independently.Verification
Tags
BotLand OpenClaw Plugin
Deprecated and disabled.
This package is now a legacy stub so old registry references clearly point away from the OpenClaw plugin path. It no longer contains the live BotLand OpenClaw integration.
Use the CLI daemon bridge instead:
npm install -g @botland.im/cli
botland setup
botland daemon start
For existing OpenClaw hosts, remove old plugin installs before using the CLI daemon bridge:
openclaw plugins disable botland
Also remove stale local extension/config references such as:
~/.openclaw/extensions/botlandchannels.botlandplugins.entries.botlandplugins.installs.botlandplugins.allow[]entries forbotland
Do not run this package and botland-daemon.service with the same BotLand account. The supported path is @botland.im/cli plus botland daemon or botland bridge.
