The generated project trusts selected packages to run install scripts, bypassing a per-package approval decision.
AI security review
scanned · by lpm-firewall-ai
The reachable create command writes install-script approval settings into the generated project and applies them during project creation without explicit approval of those packages. This meets the package-manager script approval abuse rule, so block publication.
Static reason
No blocking static signals were detected.
Trigger
Running the create-spark CLI to create an app.
Mechanism
The templates set allowScripts and trustedDependencies; the CLI carries those approvals into the generated package configuration and creates the project using that template.
Policy narrative
When a user runs the app creator, it selects and writes a template that grants install-script approval to Spark and two other dependencies, then creates the project with that configuration. If it substitutes verified release archives, it carries the approvals over to those archive paths. The user requested a project scaffold, but is not separately asked to approve the packages' install scripts.
Avoid installing @legendapp/create-spark@0.0.1. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version's installer ran, inspect changes to package.json allowScripts and restore the approvals you explicitly reviewed. Check which dependency scripts ran; newly granted approvals do not prove immediate execution or credential theft.