The package’s native asset download is consistent with its purpose, but its dependency’s postinstall automatically registers the package’s MCP tools in project agent configurations. That install-time agent setup warrants a warning under the agent extension lifecycle rule.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Installing the package, when the consumer project declares @threenative/core; setup is skipped only with THREENATIVE_SKIP_MCP_SETUP=1 or true.
Impact
Agent clients may discover and launch the package’s MCP tools without a separate setup request.
Mechanism
The @threenative/core postinstall invokes setup, which creates or updates project-scoped MCP config files with commands for ThreeNative servers.
Evidence
package.json.lpm-dependency-evidence-a3db0b15-3c26-4d55-94b4-fe3fd9a0e737/1/npm-linux/package.json.lpm-dependency-evidence-a3db0b15-3c26-4d55-94b4-fe3fd9a0e737/1/npm-linux/scripts/postinstall.mjs.lpm-dependency-evidence-a3db0b15-3c26-4d55-94b4-fe3fd9a0e737/1/npm-linux/scripts/ensure-mcp.mjs.lpm-dependency-evidence-a3db0b15-3c26-4d55-94b4-fe3fd9a0e737/1/npm-linux/mcp/install.mjs