Security audit
Security checks for vulnerabilities and agentic risk
This is a local configuration checker that reads expected project config files and reports problems, with no evidence of exfiltration, persistence, or destructive behavior.
Before installing, treat this as a local project config checker that will read your .env file. It does not appear to leak secrets, but update the npm dependencies, review any future implementation of --fix before using it, and do not rely on it to fail closed when required environment variables are missing.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
// Determine workspace root
const WORKSPACE_ROOT = path.resolve(__dirname, '../../');
const ENV_FILE = path.join(WORKSPACE_ROOT, '.env');
const OPENCLAW_JSON = path.join(WORKSPACE_ROOT, 'openclaw.json');
const PACKAGE_JSON = path.join(WORKSPACE_ROOT, 'package.json');
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
}
function checkEnv() {
log('Checking .env file...');
if (!fs.existsSync(ENV_FILE)) {
log('Error: .env file missing!', 'ERROR');
return { valid: false, issues: ['Missing .env file'] };
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
}
function checkEnv() {
log('Checking .env file...');
if (!fs.existsSync(ENV_FILE)) {
log('Error: .env file missing!', 'ERROR');
return { valid: false, issues: ['Missing .env file'] };
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
}
function checkEnv() {
log('Checking .env file...');
if (!fs.existsSync(ENV_FILE)) {
log('Error: .env file missing!', 'ERROR');
return { valid: false, issues: ['Missing .env file'] };
brace-expansion 1.1.12 is flagged with multiple DoS advisories, and it is present in the resolved dependency tree. Even though it is a transitive dev dependency, vulnerable glob/pattern expansion can still be triggered during local development or CI runs, causing excessive CPU or memory consumption.
minimatch 3.1.2 has multiple ReDoS advisories and appears in the dependency tree as a transitive dependency of glob. Crafted glob patterns can trigger catastrophic backtracking or heavy computation, which is especially relevant in CI or developer tooling that accepts untrusted patterns.
js-yaml 4.1.0 is associated with multiple CPU exhaustion issues, and the exact version is locked in this file. Although it is a dev dependency used through mocha, parsing attacker-controlled YAML in test infrastructure or automation could still enable denial of service.
minimatch 4.2.1 is separately present and flagged for ReDoS issues, so this is not duplicative of the 3.1.2 finding. Any code path that evaluates attacker-controlled glob expressions through this version may suffer excessive CPU consumption and service slowdown.
nanoid 3.3.1 is present and has advisories covering predictable output and potential infinite-loop conditions in certain generator misuse cases. In this context it is a dev dependency pulled by mocha, which lowers direct production exposure, but it can still affect tooling integrity or availability if unsafe code paths are exercised.
picomatch 2.3.1 is locked in and carries method-injection/ReDoS style advisories related to crafted glob patterns. Since picomatch is commonly used for file matching, malicious patterns in automation, tests, or developer tooling can lead to incorrect matching or denial of service.
serialize-javascript 6.0.0 has high-severity advisories including potential RCE/XSS depending on how serialized output is consumed, and the vulnerable version is present as a mocha dependency. Even in dev/test tooling, serializing attacker-controlled objects and later embedding or evaluating the result can create serious compromise paths.
The skill documentation advertises a --fix mode that can create or repair configuration files, but it does not clearly warn that running this mode may modify important project files. In an agent or automation context, unclear disclosure about write-capable behavior can lead to unintended configuration changes, overwrites, or environment drift if a user assumes the tool is read-only validation.
The script advertises that it ensures critical configurations are present, but in checkEnv() missing critical environment variables are only logged as warnings and the result is still marked valid. This can let the system proceed in a misconfigured state, causing downstream failures or insecure fallback behavior if other components assume required secrets and connection settings were verified.
diff 5.0.0 is listed with a DoS advisory affecting patch parsing/application logic, and the lockfile confirms that exact version is installed. In this skill context it is only a dev dependency via mocha, so exposure is limited to test or CI workflows unless untrusted patch data is processed there.
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
"author": "OpenClaw Evolver",
"license": "MIT",
"dependencies": {
"dotenv": "^16.0.0"
},
"devDependencies": {
"chai": "^4.3.0",
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
"dotenv": "^16.0.0"
},
"devDependencies": {
"chai": "^4.3.0",
"mocha": "^9.0.0"
},
"engines": {
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
},
"devDependencies": {
"chai": "^4.3.0",
"mocha": "^9.0.0"
},
"engines": {
"node": ">=18.0.0"