The flagged runtime behavior is consistent with the package's testing CLI and account features: the lifecycle script is a prepublish check, account credentials are sent to the stated entitlement service, and dashboard authentication stays on local API paths. Probe data writes require user action, and the update check retrieves npm package metadata.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The CLI update check runs when the CLI is invoked; account calls occur through the dashboard account flow, and probe runs require a user command or dashboard action.
Impact
No user data theft, unauthorized account action, or concealed code execution was identified in the reviewed paths.
Mechanism
The update check fetches package metadata from npm; account requests send a user-entered Kryptheon connect code to the entitlement service; dashboard tokens go to relative local API paths.
Network endpoints2
registry.npmjs.orgdkheqkynldupnxorqscd.supabase.co