@stacksjs/actions@0.75.258
The Stacks actions.
AI Security Review
scanned 14d ago · by lpm-firewall-aiSource inspection found a forced first-party agent setup during framework upgrades, creating a residual risk of unprompted project agent-instruction changes. Other flagged code was consistent with package features, and no install-time attack behavior was established.
Decision evidence
public snapshot- The package manifest has a prepublish-only build hook and no preinstall, install, or postinstall hook.
- The framework upgrade flow calls the package upgrade routine with the parsed upgrade options.
- The upgrade routine detects Codex by default and runs the project Buddy AI setup command with --force; the package declaration says canonical agent instructions are kept after updates.
- The generated action types are built from the project’s route registry and written to the framework’s generated routes file.
- The inspected discovery, lockfile, and release-note helpers inventory project packages, check lockfile consistency, and format commit notes.
- The inspected fetcher sends requests to the URL passed to its generic request method; no unrelated credential recipient was established.
- The agent setup runs during an explicit framework upgrade flow, not an npm install hook.
- The other flagged code performs project inventory, lockfile checks, route type generation, and release-note formatting.
- The inspected runtime dependencies expose action, API, and authentication library functions; their manifests show build and typecheck scripts, not install hooks.
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.258.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.258 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.