Bawwab: Top 302 scan

notfair

Not malicious, needs a look Reviewed: expected behaviour

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
nowork-studio/notfair-plugin
Commit
be3a43233c8836525fafcfdb85f78fb08e56a43f
Listed in
nowork-studio/notfair-plugin
Popularity
4,274 GitHub stars (2026-11-20)
Link
https://github.com/nowork-studio/notfair-plugin/tree/be3a43233c8836525fafcfdb85f78fb08e56a43f
Scanned
2026-11-20T23:18:42+00:00
Scan time
2.6 s
Scanned as
plugin
Review note: The only flag is the plugin's logo image.

Findings (1)

files.truncated: Scan limit reached med

assets/notfair-icon.png

assets/notfair-icon.png contains NUL bytes; not scanned

What this means: Some files, or the tail of a very large file, were not scanned, so malicious code could hide in them.

The rule's general advice: Review the unscanned files manually or raise the limits. (see the review note for this case)

Expected for what this tool does

The plugin logo named in plugin.json and .codex-plugin/plugin.json. Checked by hand: it is a real 512x512 PNG and nothing runs it.

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

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

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

[server NotFair] 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-nowork-studio-notfair-plugin-eb0776.