Bawwab: Top 302 scan

amazon-location-service

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
awslabs/agent-plugins / plugins/amazon-location-service
Commit
097fe8ad56d8a1d5e2c81d7880adf145553cf244
Listed in
anthropics/claude-plugins-official
Popularity
947 GitHub stars (2026-11-20) (official, always included)
Link
https://github.com/awslabs/agent-plugins/tree/097fe8ad56d8a1d5e2c81d7880adf145553cf244/plugins/amazon-location-service
Scanned
2026-11-20T23:26:12+00:00
Scan time
2.5 s
Scanned as
plugin
Review note: One fetch error: the scanner misread a uvx '@latest' spec, so AWS's MCP proxy package went unscanned. Nothing suspicious was found.

Findings (1)

fetch.failed: Target could not be fetched med

[server aws-mcp] GET https://pypi.org/pypi/mcp-proxy-for-aws%40latest/json returned HTTP 404

What this means: The package or server could not be downloaded, so nothing was reviewed.

The rule's general advice: Check the name, version and network, then retry. (see the review note for this case)

Known false alarm

.mcp.json runs 'uvx mcp-proxy-for-aws@latest https://aws-mcp.us-east-1.api.aws/mcp'. Bawwab treated 'mcp-proxy-for-aws@latest' as the package name, which returns 404 on PyPI. This is a scanner parsing error, not a missing or suspicious package. The proxy (AWS's own, unpinned) was not scanned here.

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

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

Dispute this result

Maintainer and think this is wrong? Open a dispute on GitHub with the target id plugin-awslabs-agent-plugins-plugins-amazon-location-service-d34693.