The scanner signals resolve to package-aligned behavior: an explicit product installer and authentication to DingTalk's own API. The test setup's child process is guarded by a missing generated-client check, and no package lifecycle hook was identified.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI installation behavior runs when a user invokes the package's install command; token retrieval occurs when the service requests a DingTalk access token.
Impact
No credential exfiltration or unconsented install-time mutation was established.
Mechanism
The CLI copies product files into its dedicated home directory and installs dependencies with lifecycle scripts disabled. The token manager sends configured DingTalk credentials to the DingTalk token API.
Network endpoints1
oapi.dingtalk.com/gettoken