suppa-mcp-2@1.41.0
MCP server for the Suppa platform (modern.suppa.me) — Tasks, Docs/Pages, Entities & Schema, Forms, Automations, and file attachments, with multi-tenant Google auth. Node port of PyPI suppa-mcp.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe automatic postinstall performs unconsented writes to a consuming project’s agent configuration and instructions, which meets the policy for blocking lifecycle mutation of an agent control surface. Project-specific gating and an opt-out reduce exposure but do not establish consent.
Decision evidence
public snapshot- The manifest runs the guard installer from an automatic postinstall hook.
- The postinstall skips CI, global installs, and the package’s own install, then requires a Suppa app; it has no consent prompt.
- The installer adds hooks to Claude’s PreToolUse, PostToolUse, and Stop events, and writes the updated settings file.
- The installer creates or updates AGENTS.md and CLAUDE.md in the consumer repository.
- The installer invokes routines that install agent hooks, agent instruction files, a git hook, CI configuration, and an npm script.
- The postinstall has an explicit environment-variable opt-out and skips unrelated projects without Suppa schema code or a Suppa SDK dependency.
Source & flagged code
12 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/auth.jsFindings
Affected versions and remediation
This report applies to suppa-mcp-2@1.41.0.
See all versions of suppa-mcp-2 for other recorded verdicts.
- Avoid installing suppa-mcp-2@1.41.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.