The launcher’s default CLI path fetches and executes code from the project’s own repository, serving the advertised application, but that runtime execution is not disclosed in the README and the fetched code is absent from this snapshot. The remote-code rule blocks undisclosed remote execution on a default start path, so the block still applies with dangerous-capability intent.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
User runs the documented `riot` command.
Mechanism
The launcher calls `uv tool run --from` with the default Git source and runs its `riot` entry point. The source is the package’s own repository, but the runtime fetch and execution are not disclosed in the README.
Attack narrative
When a user runs the documented `riot` command, the launcher uses `uv tool run --from` to fetch and execute the `riot` application from its default GitHub repository. That repository matches the package’s declared repository and the source appears to serve the advertised application, but the fetched Python code is outside this snapshot and the README does not disclose the runtime fetch-and-execute behavior. The default command therefore runs uninspectable remote code.
Evidence
bin/riot.jspackage.jsonREADME.md