@stacksjs/actions@0.75.268
The Stacks actions.
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe manifest has no install-time lifecycle hook, and the cited network, action-runner, project-discovery, and type-generation code fits the package's tooling role. The agent setup refresh is reached from an explicit framework upgrade command; the inspected source does not establish malicious or unconsented lifecycle behavior.
Decision evidence
public snapshot- package.json declares only a prepublishOnly hook, which runs the build; its main entry exports package APIs.
- Agent provider detection and setup refresh appear in the framework upgrade flow, not an npm lifecycle hook.
- The inspected API dependency exports a generic fetch client; the excerpt shows a caller-supplied URL and request body.
- The action runner lazily imports this package only when an action is requested; route type generation creates generated type content.
- The inspected auth dependency exposes authentication and OAuth APIs through its package entrypoint.
- Package discovery reads project manifests, and pantry-lock code compares lockfile data with declarations.
Source & flagged code
4 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.268.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.268 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.