Bawwab: Top 302 scan

expo

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
expo/skills / plugins/expo
Commit
d4f484024fec15196bfd3c272e953e3f983972cf
Listed in
anthropics/claude-plugins-official
Popularity
4,195 GitHub stars (2026-11-20) (official, always included)
Link
https://github.com/expo/skills/tree/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo
Scanned
2026-11-20T23:18:44+00:00
Scan time
2.2 s
Scanned as
plugin
Review note: The only flag is the plugin's PNG logo.

Findings (1)

files.truncated: Scan limit reached med

assets/expo.png

assets/expo.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

A real PNG image used as the plugin's logo in its manifest. Bawwab does not scan images and flags any file a manifest names; checked by hand, it is a valid PNG and nothing in the plugin 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 expo] remote server answered HTTP 403; 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-expo-skills-plugins-expo-326cd2.