@stacksjs/actions@0.75.308
The Stacks actions.
AI Security Review
scanned 10d ago · by lpm-firewall-aiSource inspection found no concrete malicious behavior. The flagged network, dynamic import, dependency bridge, and generated-file operations are consistent with the package’s action, release, lint, and project-generation functions.
Decision evidence
public snapshot- package.json exposes dist entrypoints; its only lifecycle script is prepublishOnly, which runs the build.
- The runtime hints resolve to a generic caller-directed HTTP client and a route-type generator that writes generated metadata.
- The inspected action-runner, API, and auth dependencies expose expected runtime modules; their manifests show build and typecheck scripts, not install hooks.
- Package discovery writes a generated manifest from discovered package metadata; pantry-lock checks declarations and resolved versions.
- GitHub release publishing obtains a GitHub token and sends it to the GitHub API for the repository derived from the project origin; the bump caller supports dry runs.
- No concrete malicious behavior or unintended credential transfer was identified in the inspected source.
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.308.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.308 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.