@extenshi/mcp@0.10.0
Extenshi MCP server — bring the extension catalog (search, security, market research) and pre-publish scanning into your AI tools
AI Security Review
scanned 26d ago · by lpm-firewall-aiThe lifecycle hook’s ping requires a previously recorded positive telemetry setting and carries install metadata rather than API credentials. The inspected runtime network behavior is consistent with package telemetry and documentation, with no confirmed attack surface.
Decision evidence
public snapshot- package.json defines a postinstall hook, and the hook sends only after finding telemetry explicitly set to true in the existing config.
- The install event contains package/runtime metadata and an anonymous install ID; no API credential is included in the inspected payload construction.
- Documentation lookup fetches text from the package’s Extenshi documentation service.
- The development guide exposes documented extension development and research tools.
Source & flagged code
5 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references dynamic require/import behavior.
dist/index.jsView on unpkg · L29Findings
Affected versions and remediation
This report applies to @extenshi/mcp@0.10.0.
See all versions of @extenshi/mcp for other recorded verdicts.
- Review the evidence and your use of @extenshi/mcp@0.10.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.