@stacksjs/actions@0.75.221
The Stacks actions.
AI Security Review
scanned 18d ago · by lpm-firewall-aiInspected source shows no install lifecycle trigger for the flagged behavior. The AI setup refresh occurs in the explicit framework upgrade path, while the other flagged operations serve project discovery, dependency checks, or GitHub release actions; no concrete attack was identified.
Decision evidence
public snapshot- package.json defines only a prepublishOnly build hook; it has no install lifecycle hook.
- The upgrade helper detects AI provider files, including Codex and project-local provider markers.
- Package discovery reads project dependencies and writes a generated discovery manifest.
- The pantry-lock module checks declared dependency ranges against resolved versions.
- The AI setup refresh is called from the framework package upgrade path.
- The flagged AI setup command is reached through an explicit package upgrade operation; source inspection found no install-time activation for it.
- GitHub release support reads GitHub credentials and targets the GitHub API, matching its stated service function.
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.221.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.221 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.