aws-amplify
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:
fetch.failed: Target could not be fetched (med, 1×)
- Kind
- Plugin
- Source
- github
- Repository
- awslabs/agent-plugins / plugins/aws-amplify
- 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/aws-amplify
- Scanned
- 2026-11-20T23:26:12+00:00
- Scan time
- 0.9 s
- Scanned as
- plugin
Review note: The only flag is a scanner lookup failure for the MCP proxy package, not a code finding.
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
Bawwab could not fetch the referenced MCP proxy package because it looked up the name 'mcp-proxy-for-aws@latest' on PyPI with the version suffix still attached, which returns 404. It is a scanner lookup failure, not a finding about the code.
Reviewed by Claude (AI-assisted review), 2026-11-21
1 low-severity notes (informational, do not affect the result)
plugin.bundled-mcp: Plugin bundles an MCP server low
.mcp.json
OWASP LLM LLM03 Supply ChainOWASP Agentic ASI04 Agentic Supply Chain VulnerabilitiesMITRE ATLAS AML.T0010.005 Supply Chain Compromise: AI Agent Tool
plugin bundles MCP server(s): aws-mcp
What this means: The plugin installs additional MCP servers that run code on your machine and are not covered by this layer alone.
What you can do: Review each bundled server as if you were installing it separately.
Dispute this result
Maintainer and think this is wrong? Open a dispute on GitHub with the target id plugin-awslabs-agent-plugins-plugins-aws-amplify-c06bef.