@stacksjs/actions@0.75.334
The Stacks actions.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe inspected entry point registers the package’s action runner, and the flagged bridge provides its expected fallback for running named actions. Deployment credentials and GitHub release operations are tied to deployment or release functionality; no unrelated automatic transfer or harmful action was found.
Decision evidence
public snapshot- Metadata identifies the package as @stacksjs/actions@0.75.334 in the Stacks repository.
- The only lifecycle script is prepublishOnly, which runs the package build.
- The root entry registers the action runner and re-exports package functions; it contains no credential or network operation.
- The inspected action-runner bridge falls back to importing @stacksjs/actions to run a named action, matching its stated purpose.
- Package discovery reads Stacks metadata from installed packages and pantry package manifests.
- GitHub release publishing is exposed as a function and operates on the repository origin supplied by the caller.
- Deployment code supports reading AWS credentials from project environment files and using them for AWS deployment operations; this is consistent with the package’s deployment functionality.
- The package has dynamic imports and filesystem operations in command and generation modules, but the inspected code ties them to those functions rather than an install-time credential transfer.
- Scanner flags for a dependency bridge, possible secret pattern, dynamic import, and a changed source file did not establish an unrelated automatic action.
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.334.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.334 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.