The package pins a dependency version covered by a policy warning because fewer than half of that dependency’s releases are blocked. More concretely, the dependency’s reachable postinstall modifies project agent configs to register its own MCP servers, which warrants a warning under the agent extension lifecycle rule.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing this package when the consumer project declares @threenative/core; setup runs unless THREENATIVE_SKIP_MCP_SETUP is set.
Impact
The installation changes which MCP tools are available to agents working in that project. This is an agent extension lifecycle risk, not evidence of malicious behavior.
Mechanism
The dependency merges its server entries into project-scoped agent configuration files and writes changed files.
Evidence
package.json.lpm-dependency-evidence-f69a4d31-79bd-4c99-a92b-9f323dd0a35c/1/npm-linux/package.json.lpm-dependency-evidence-f69a4d31-79bd-4c99-a92b-9f323dd0a35c/1/npm-linux/scripts/postinstall.mjs.lpm-dependency-evidence-f69a4d31-79bd-4c99-a92b-9f323dd0a35c/1/npm-linux/scripts/ensure-mcp.mjs.lpm-dependency-evidence-f69a4d31-79bd-4c99-a92b-9f323dd0a35c/1/npm-linux/mcp/install.mjs