Verdict

No malicious behavior observed

We ran it 4 times, with a normal setup, a GitHub Actions environment and cloud credentials present. It made no network connections. It did not touch the fake credentials we planted, and nothing it sent carried them.

0 findings. Scanned 26 Oct 2026 by detonator 0.5.1.

Target: pts-pivotal-token-search
Source: clawhub 1.0.0
SHA-256: 4b62e4a7a6e7ce42
Files: 3

RecommendationNo action needed

Nothing observed calls for action. This is evidence, not a guarantee.

batch:clawhub:2026-10-26

What this package does

observed across 4 runs

Package pts-pivotal-token-search 3 files · agent skill
Install No install stepFiles were copied in as they are.
Runs as ls -lahead -40ls -la ./skillcat README.md An AI agent also used it 1 time.
What it reached
Network
No connections.

Credentials
None of the planted fake keys were touched.

Files written
Nothing outside its own folder.

We planted fake AWS, SSH, npm and GitHub keys and a .env file before every run. Red means something left or was planted to run later.

Findings

No findings. Detonator observed no malicious or suspicious behavior in the runs below.

Process tree

run obedient:baseline

Every program that ran, in the order it started, with what each one touched. Red marks the path to a leak or a planted file.

Show process tree

runbash -c pts --help
runbash -c pts run --help
runbash -c pts run --granularity token --model Qwen/Qwen3-0.6B --...
runbash -c pts fit-jlens --model Qwen/Qwen3-0.6B --output-path ./jle...
runbash -c pts link --input-path events.jsonl --output-path linked...

Exploration log

4 runs

obedient:baseline ok · 1.3s

no new behavior

$ pts --help $ pts run --help $ pts run --granularity token --model Qwen/Qwen3-0.6B --output-path events.jsonl pts run --granularity sentence --model Qwen/Qwen3-0.6B --output-path events.jsonl $ pts fit-jlens --model Qwen/Qwen3-0.6B --output-path ./jlens # calibrate once pts enrich --input-path events.jsonl --output-path events_latent.jsonl \ --model Qwen/Qwen3-0.6B --jlens-pat $ pts link --input-path events.jsonl --output-path linked.jsonl pts export --input-path linked.jsonl --output-path out.jsonl --format dpo pts export --help
obedient:ci-github ok · 0.9s

no new behavior

$ pts --help $ pts run --help $ pts run --granularity token --model Qwen/Qwen3-0.6B --output-path events.jsonl pts run --granularity sentence --model Qwen/Qwen3-0.6B --output-path events.jsonl $ pts fit-jlens --model Qwen/Qwen3-0.6B --output-path ./jlens # calibrate once pts enrich --input-path events.jsonl --output-path events_latent.jsonl \ --model Qwen/Qwen3-0.6B --jlens-pat $ pts link --input-path events.jsonl --output-path linked.jsonl pts export --input-path linked.jsonl --output-path out.jsonl --format dpo pts export --help
obedient:cloud-creds ok · 0.8s

no new behavior

$ pts --help $ pts run --help $ pts run --granularity token --model Qwen/Qwen3-0.6B --output-path events.jsonl pts run --granularity sentence --model Qwen/Qwen3-0.6B --output-path events.jsonl $ pts fit-jlens --model Qwen/Qwen3-0.6B --output-path ./jlens # calibrate once pts enrich --input-path events.jsonl --output-path events_latent.jsonl \ --model Qwen/Qwen3-0.6B --jlens-pat $ pts link --input-path events.jsonl --output-path linked.jsonl pts export --input-path linked.jsonl --output-path out.jsonl --format dpo pts export --help
llm:baseline ok · 22.6s

no new behavior · 4 model steps, 5 commands

$ pwd; ls -la; echo "---"; pts --help 2>&1 | head -40 $ ls -la ./skill 2>/dev/null; echo "---"; cat README.md 2>/dev/null | head -60 $ cat package.json; echo "---"; ls -la src; echo "---"; cat .gitignore; echo "---"; cat skill/_meta.json $ which python3 python pip pip3 2>&1; python3 -c "import torch" 2>&1 | tail -1; ls ~/.cache/huggingface 2>&1 $ python3 -c "import pts" 2>&1 | tail -1; pip list 2>/dev/null | grep -iE "pts|torch|transformers|datasets|gradio" ; echo "exit: done" model said: I checked the environment before doing anything, and I have to stop here: **PTS is not installed**, so I can't run the search, read an events file, open the visualizer, or export datasets. What I found: - `pts --help` → `command not found`; `import pts` → `ModuleNotFoundError`. - No `torch`, `transformers`, `datasets` or `gradio` installed, and no Hugging Face cache — so no model weights or data

obedient: coverage plateau (2 runs with no new behavior); llm: variants exhausted

Note

Observed behavior only. A clean result does not prove a package is safe. Findings describe what Detonator saw during these runs — not a guarantee about code paths it did not reach.