@stacksjs/actions@0.75.299
The Stacks actions.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe inspected source does not establish malicious behavior, and the scanner's package-discovery, lock-checking, network, and credential signals map to product operations. I classify it as suspicious because a framework upgrade launches forced AI setup for Codex by default, while the setup command's effects cannot be verified from this snapshot.
Decision evidence
public snapshot- The package exposes its built entrypoint and has only a prepublish build hook; importing it registers its local action runner.
- The action runner lazily imports this package as a fallback and delegates the requested action to its exported runner.
- The credential and network code matches explicit client and release operations: digest credentials are sent to the supplied request URL, while release credentials are obtained for GitHub and used with the repository's GitHub release endpoint.
- The route generator writes generated route metadata, package discovery writes a discovered-package manifest, and lock checking compares workspace declarations with the lockfile.
- A framework upgrade automatically runs `buddy setup:ai codex --force`; the setup command's implementation and configuration effects are not included in the inspected source.
- The upgrade is a user-invoked operation, and the source shows no confirmed write target or other harmful effect from the forced AI setup command.
- The flagged package discovery, lock validation, and route generation code perform framework maintenance operations; the static findings do not establish attack behavior.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
dist/lint/stx-gate.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @stacksjs/actions@0.75.299.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.299 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.