The package is suspicious because its published bundle contains a publisher-side GitHub Actions OIDC credential, creating a serious exposure vulnerability. I found no install hook or runtime path that automatically sends the token, so the source does not establish malicious exfiltration.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Consumers receiving or inspecting the package bundle can access the embedded credential; package import or installation is not needed to expose its bytes.
Impact
The credential could enable access within its GitHub Actions scope while valid. The source does not establish whether it remains usable.
Mechanism
The CommonJS entrypoint contains a build-time environment snapshot with an ACTIONS_ID_TOKEN_REQUEST_TOKEN value and workflow identity data.
Evidence
dist-lib/questions.cjs.jspackage.json