@stacksjs/actions@0.75.291
The Stacks actions.
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe manifest’s only lifecycle script runs a build before publication. Inspected flagged code performs framework and package-management functions, and the network request path uses a caller-supplied URL; no concrete malicious behavior was found.
Decision evidence
public snapshot- package.json exposes JavaScript entry points and has only a prepublish build hook.
- The action-runner dependency calls this package’s runAction export when no runner has been registered; this is an explicit action-dispatch bridge.
- The API fetcher sends requests to the URL supplied by its caller, with configured headers and body.
- The route type generator writes generated route metadata to the framework’s auto-imports directory.
- Package discovery reads Stacks package metadata and writes a discovered-packages manifest.
- The lockfile checker compares workspace declarations with the lockfile, while package upgrade logic reconciles Stacks package versions.
- The scanner flagged dynamic imports, network APIs, environment access, and a semantic-analysis limit; inspected source shows framework tooling and caller-directed HTTP behavior, not a concrete attack.
- The action-runner dependency links back to this package for named action dispatch; its manifest has no install lifecycle hook.
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.291.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.291 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.