deepline-feedback — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited deepline-feedback (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Send feedback or a bug report to the Deepline team.
/deepline-feedback the waterfall broke). Otherwise ask the user.This report will include:
>
- Your feedback: {feedback text} - Environment info (auto-collected) - Current session transcript
>
Send this feedback?
Options: "Send it" / "Cancel".
deepline feedback send "{feedback text}" --json deepline sessions send --current-session --jsonIf that reports no session files and ~/mnt/.claude/projects exists, the run is likely in Cowork. Bridge the mounted transcript directory, then retry. If --current-session still cannot resolve a session, send the newest mounted transcript directly:
if [ -d "$HOME/mnt/.claude/projects" ]; then
mkdir -p "$HOME/.claude"
ln -sfn "$HOME/mnt/.claude/projects" "$HOME/.claude/projects" 2>/dev/null || true
deepline sessions send --current-session --json || deepline sessions send --file "$(ls -t "$HOME"/mnt/.claude/projects/*/*.jsonl | head -1)" --json
fiUse the plural sessions send command, not the old singular session form.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.