lumos-upgrade-version
Pass
Audited by Gen Agent Trust Hub on Sep 24, 2026
Risk Level: SAFEEXTERNAL_DOWNLOADSREMOTE_CODE_EXECUTIONCOMMAND_EXECUTIONINDIRECT_PROMPT_INJECTION
Full Analysis
- [EXTERNAL_DOWNLOADS]: The skill fetches framework source archives and configuration files from the official GitHub repository at
github.com/lumosframework/lumos-for-astro. This is a documented vendor resource and follows standard update procedures. - [REMOTE_CODE_EXECUTION]: Framework code is downloaded via
curland extracted usingtarto create a merge base for the migration. This code is sourced from a trusted vendor repository and is used to identify differences between framework versions. - [COMMAND_EXECUTION]: The skill automates several CLI tools to manage the upgrade process:
- Uses
gitto commit changes and manage the migration state. - Uses
npmandnpxto update project dependencies and run framework-specific upgrade tools like@astrojs/upgrade. - Uses
astroto run the development server and verify the build status. - The
visual-check.mjsscript executes local browser binaries (Google Chrome, Chromium, or Microsoft Edge) usingexecFileto capture screenshots of the site routes. - [INDIRECT_PROMPT_INJECTION]: The skill possesses a data ingestion surface by reading the project's
package.jsonfor version metadata and scanning thesrc/pagesdirectory to map site routes. - Ingestion points:
package.jsonand local filesystem scan of thesrc/pagesdirectory. - Boundary markers: None present.
- Capability inventory: Execution of shell commands (
git,npm,astro), browser execution viaexecFile, and filesystem write access viatarand thesharpimage library. - Sanitization: The skill uses a
slugfunction to sanitize filenames for screenshots and employsexecFileinstead ofexecto prevent shell-based command injection when invoking browser binaries. This behavior is consistent with the primary purpose of a migration tool and is considered safe.
Audit Metadata