@stacksjs/actions@0.75.287
The Stacks actions.
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected runtime hits are consistent with the package’s exported framework functions. The API fetcher’s credentials and destination are supplied by its caller; no package-selected recipient or concrete attack behavior was found.
Decision evidence
public snapshot- package.json defines only a build-only prepublish hook; it has no preinstall, install, or postinstall hook.
- The action-runner snapshot has build and typecheck scripts, and its helper lazily imports this package only when an action is requested.
- The API fetcher sends requests to its supplied URL and uses caller-provided digest credentials; the inspected code does not select a credential recipient.
- The inspected action-runner, API, and authentication dependency snapshots expose build or library functionality without an install-time hook.
- Package discovery reads project package metadata and writes a generated discovered-packages manifest.
- The pantry-lock helper checks declared dependencies and toolchain pins; it does not install packages or execute commands.
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.287.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.287 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.