@stacksjs/actions@0.75.305
⚠ Under reviewThe Stacks actions.
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe reviewed lifecycle and flagged package code show no concrete attack, and the dynamic import and network signals have ordinary package functions. The manifest declares a broad runtime dependency graph whose behavior was not fully available for source inspection, so the verdict remains unresolved.
Decision evidence
public snapshot- The manifest’s only lifecycle hook runs the package build before publishing.
- The main entrypoint registers an action runner and exports the package API.
- The package declares many runtime dependencies; inspected snapshots include runner, API, and authentication modules.
- The API helper sends requests to the supplied URL with configured headers and body.
- The lint helper imports a project-local config after locating it.
- The inspected package code shows framework discovery, lock validation, route type generation, and GitHub release helpers; no concrete attack was identified there.
- Several declared runtime dependencies were outside the inspected source set, leaving their behavior unresolved.
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.305.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.305 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.