The published CommonJS entrypoint embeds a JWT-like GitHub Actions OIDC request token and workflow metadata from the publisher's build environment. This is a serious credential exposure, but the inspected source does not show the token being transmitted or used, so the evidence supports a warning rather than a malicious-package block.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
The token is available to anyone who obtains the published bundle; it is embedded in the package's CommonJS entrypoint.
Impact
The token could expose the publisher's workflow identity while valid. No outbound transfer or use of the token was identified in the inspected code.
Mechanism
A build-time environment snapshot was included in dist-lib/questions.cjs.js, carrying ACTIONS_ID_TOKEN_REQUEST_TOKEN and GitHub workflow identifiers.
Evidence
dist-lib/questions.cjs.js