The flagged metadata strings are part of a request-header denylist, not metadata access. Lifecycle scripts build the bundled Lisp runtime locally, and inspected credential handling matches configured provider use.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Package installation runs the postinstall and prepare scripts; provider requests occur when the plugin uses a configured model.
Impact
No unrelated credential collection, metadata retrieval, or unauthorized account action was identified in the inspected source.
Mechanism
The install hook invokes the bundled runtime builder with the local Lisp source and local SBCL. The provider SDK sends its API key to the provider endpoint, defaulting to OpenAI when using that provider.
Evidence
scripts/install-lisp.mjsdist/dsh/lisp/installed-runtime.jslisp