Smart Git Backup

• Verdict: Pass
• Analyzed: May 12, 2026, 3:59 AM
• Findings: 0
• Version: 1.0.0
• Hash: 82aaa16cfe4d7fa1942bdaae2610eb98d8ccaf380aa53165d1c048e82a44a9c2
• Source: palm
• External report: View on VirusTotal

Overview

Type: OpenClaw Skill Name: memory-git-sync Version: 1.0.0 The skill 'memory-git-sync' is designed to automate Git synchronization and backup of the OpenClaw workspace. Both the `SKILL.md` and `scripts/sync.sh` align with this stated purpose, using standard `git` and `bash` commands for repository management, validation, and conflict resolution. There is no evidence of intentional harmful behavior, data exfiltration, backdoor installation, or prompt injection designed to subvert the agent's core directives. The script includes robust error handling and structured logging, making it transparent and functional.

Findings (0)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

ASI02: Tool Misuse and Exploitation

ConcernHigh Confidence

What this means

If run in the wrong repository or before review, private workspace files or unintended changes could be committed and pushed to the remote Git repository.

Why it was flagged

The script broadly stages all changes, creates a commit, and pushes to the configured remote without an enforced confirmation or file allowlist.

Skill content

git add .
...
git commit -m "$MSG"
...
git push origin "$CURRENT_BRANCH"

Recommendation

Run only after checking `git status` and `git diff`, use a private trusted remote, maintain a strict `.gitignore`, and consider adding a dry-run or confirmation step before `git add`, `commit`, and `push`.

ASI03: Identity and Privilege Abuse

NoteMedium Confidence

What this means

Repository details, and in poorly configured remotes possibly credentials, could appear in agent logs or command output.

Why it was flagged

The script prints the full configured remote URL. Some Git remotes may include usernames, private repository paths, or embedded tokens.

Skill content

REMOTE_URL=$(git remote get-url origin)
log_success "Remote 'origin' configured: $REMOTE_URL"

Recommendation

Use SSH keys or a credential helper rather than embedding tokens in remote URLs, and mask or avoid printing full remote URLs in logs.

ASI06: Memory and Context Poisoning

NoteMedium Confidence

What this means

If the remote repository is shared or compromised, remote changes could alter local workspace memory or files that future agent sessions may rely on.

Why it was flagged

The skill syncs workspace memory with a remote repository and pulls remote changes back into the workspace, which can persist and reintroduce remote content across tasks.

Skill content

Automates Git synchronization and backup of workspace memory to a remote repository.
...
**Pulls** latest remote changes to avoid conflicts

Recommendation

Use a trusted private repository, restrict write access, and review incoming remote changes before relying on synced workspace memory.