The inspected startup and credential flows have package-related purposes: updates come from the official npm registry with install scripts disabled, and provider keys are sent to their corresponding model APIs for model discovery. The flagged metadata path implements checks against private and link-local destinations, and the shell patterns appear in safeguards rather than automatic download-and-run behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
The updater runs when the CLI starts in a managed installation; model discovery runs when the application resolves provider models.
Impact
No unrequested credential disclosure, unrelated code execution, or other malicious behavior was found in the reviewed paths.
Mechanism
The updater checks registry.npmjs.org and installs this package with scripts disabled. Provider discovery queries a provider's models endpoint with that provider's configured key. Browser URL validation blocks private and internal addresses.
Evidence
src/autoUpdate.jssrc/dynamicCatalogue.tssrc/browser/urlPolicy.js
Network endpoints8
registry.npmjs.org/@causyne%2fagent/latest/v1/models