@stacksjs/actions@0.75.401
The Stacks actions.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged AWS credential access occurs in deployment logic and is consistent with the package’s purpose. The reviewed entry point and lifecycle script show no evidence of automatic credential collection or unrelated external contact.
Decision evidence
public snapshot- The only lifecycle script is prepublishOnly, which runs the package build.
- The deployment code reads AWS settings from project environment files as part of deployment behavior.
- The package entry point registers and exports action functionality; no credential collection is shown there.
- SSL setup is exposed as a function that takes options and uses the configured domain.
- The flagged deployment code accesses AWS credentials and performs deployment operations, which match the package’s framework-actions purpose.
- The SSL setup code can write hosts and certificate files when invoked, consistent with its setup function.
Source & flagged code
16 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.401.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.401 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.