Static inspection found no concrete attack behavior. The scanner flags resolve to user-invoked installation, intended DingTalk authentication, test setup, and ordinary Fastify plugin code.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The CLI installer runs when a user invokes its install command; the test setup runs during test initialization if a generated client is absent.
Impact
The inspected behavior supports installation and normal DingTalk authentication; no credential transfer to an unrelated recipient or other concrete attack was found.
Mechanism
The installer copies the service and installs production dependencies with lifecycle scripts disabled. The token manager requests a DingTalk access token using configured DingTalk credentials.
Evidence
package.jsonscripts/cli.mjsdist/src/integrations/dingtalk/token-manager.jsdist/tests/global-setup.js.lpm-dependency-evidence-69107dc2-ccba-48fa-9371-d94343422313/0/npm-linux/package.json.lpm-dependency-evidence-69107dc2-ccba-48fa-9371-d94343422313/0/npm-linux/index.js.lpm-dependency-evidence-69107dc2-ccba-48fa-9371-d94343422313/1/npm-linux/package.json