@stacksjs/actions@0.75.237
The Stacks actions.
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe package has no npm install hook, but its explicit upgrade flow automatically runs a forced AI setup command for detected providers. Because the command’s effects are outside the inspected source, a warning is appropriate while agent-configuration impact remains unresolved.
Decision evidence
public snapshot- The manifest defines only a prepublishOnly build lifecycle script; it has no install hook.
- The upgrade code detects existing agent providers, then runs a forced AI setup command for each detected provider.
- The package exposes upgrade functionality, but the invoked setup command’s configuration effects are not established by the inspected source.
- The agent setup command is invoked from the framework upgrade flow, not from an npm install hook.
- Provider detection checks for existing agent markers; the inspected code does not show a credential transfer or network request in this path.
- The flagged package-discovery and pantry-lock code concerns generating a package manifest and checking lockfile consistency.
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.237.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.237 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.