@sapiom/mcp@0.14.0
Local Sapiom developer MCP server (sapiom-dev) — the unmetered surface for building and operating on Sapiom; today it scaffolds, tests, deploys, and inspects orchestrations. Not the remote Sapiom capability MCP.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe scanner's reverse-shell match is a false positive: the code opens a browser for OAuth and exchanges an authorization code. The package has no install lifecycle hook, and its networked publishing behavior is explicit, credential-gated functionality.
Decision evidence
public snapshot- The manifest declares development and start scripts but no automatic install lifecycle hook.
- The flagged child-process code is a browser opener inside an authentication function, not a reverse shell.
- The publishing tool requires cached credentials and is invoked as a named MCP tool before collecting and uploading a project bundle.
- No install-time execution or runtime dependency on this package itself was found.
- The OAuth callback binds locally and validates a random state value.
- The publishing tool skips dotfiles, node_modules, the project configuration file, and symlinks while collecting a bundle.
- No credential harvesting or unconsented exfiltration behavior was found.
Source & flagged code
6 flaggedSource matches reverse-shell style process and socket wiring.
dist/auth.jsView on unpkg · L1A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
Findings
Affected versions and remediation
This report applies to @sapiom/mcp@0.14.0.
See all versions of @sapiom/mcp for other recorded verdicts.
- Review the evidence and your use of @sapiom/mcp@0.14.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.