Bawwab: Top 302 scan

codspeed

Not malicious, needs a look Reviewed: false alarm

Bawwab's static rules found patterns that deserve a human look. This is not a finding that the package is malicious; the review notes below say what each pattern turned out to be.

Why it was flagged

The static rules marked this “Not malicious, needs a look” because of:

Kind
Plugin
Source
github
Repository
CodSpeedHQ/codspeed
Commit
59cfc90540bb3717d8acf4ad03f7b5531c8e1a3d
Listed in
anthropics/claude-plugins-official
Popularity
396 GitHub stars (2026-11-20) (official, always included)
Link
https://github.com/CodSpeedHQ/codspeed/tree/59cfc90540bb3717d8acf4ad03f7b5531c8e1a3d
Scanned
2026-11-20T23:28:40+00:00
Scan time
27.2 s
Scanned as
plugin
Review note: The curl-to-shell is in the project's own release CI, not in anything a user runs.

Findings (1)

remote-code.pipe-shell: Pipes a download into a shell high

.github/workflows/release.yml:67

OWASP LLM LLM03 Supply ChainOWASP Agentic ASI04 Agentic Supply Chain VulnerabilitiesOWASP Agentic ASI05 Unexpected Code Execution (RCE)MITRE ATLAS AML.T0050 Command and Scripting InterpreterCWE CWE-494 Download of Code Without Integrity Check

run: "curl --proto '=https' --tlsv1.2 -LsSf https://github.com/axodotdev/cargo-dist/releases/download/v0.31.0/cargo-dist-installer.sh | sh"

What this means: Executes whatever the remote server returns, unreviewed.

The rule's general advice: Download, verify a checksum, then run. (see the review note for this case)

Known false alarm

The project's GitHub Actions release workflow installs a pinned cargo-dist (v0.31.0) from its GitHub release with curl | sh, the standard cargo-dist setup. It runs only in the maintainers' CI, never on a user's machine.

Reviewed by Claude (AI-assisted review), 2026-11-21

4 low-severity notes (informational, do not affect the result)

fetch.auth-required: Remote server requires sign-in low

[server CodSpeed] remote server answered HTTP 401; sign-in required

What this means: The remote server requires sign-in; its tool descriptions could not be read. Bawwab re-checks at session start.

What you can do: Sign in through Claude; Bawwab re-checks the tool descriptions at session start.

Dispute this result

Maintainer and think this is wrong? Open a dispute on GitHub with the target id plugin-codspeedhq-codspeed-b6050e.