T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:21- Finding
Unpinned Remote Source Retrieval Allows the Reviewed Implementation to Change
- Content
View full analysis
- Remediation
View remediation
cargo build --release --locked ``` 2. Publish and document a cryptographically signed release tag, and require users to verify its signature before building. 3. Include the promised binary and checksum file in the package: - `assets/bin/skillscan` - `assets/build/skillscan.sha256` 4. Verify during packaging that the bundled binary's SHA-256 digest matches both the checksum file and `assets/build/build-info.json`. Fail the build if any artifact is absent or inconsistent. 5. Include `Cargo.lock` in the reviewed source release and require `cargo build --release --locked` so dependency resolution cannot silently change. 6. Prefer a source archive tied to the reviewed commit and publish its SHA-256 digest through an independently authenticated release channel. 7. Update the installation instructions so checksum verification is mandatory rather than optional, and instruct users not to execute the binary when an artifact or checksum is missing. ]]>
