@stacksjs/actions@0.75.318
The Stacks actions.
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe inspected network client uses the URL and headers supplied by its caller, and the flagged runtime operations resolve to route or package metadata generation. The manifest and inspected dependency entrypoints show no install-time attack behavior.
Decision evidence
public snapshot- The package exposes runtime modules and has only a prepublish build hook; its manifest shows no install-time hook.
- The action runner imports this package only when a caller asks it to run a named action.
- The API client sends requests to the URL passed to it, with headers configured on the client.
- The inspected generator writes route metadata, while package discovery writes package metadata and the lock checker validates dependency consistency.
- The inspected dependency manifests expose their library entrypoints and show no consumer install hooks.
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.318.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.318 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.