Caveat verdict

releaseguard

88
๐ŸŸข Trusted
No high-risk patterns surfaced by the deep scan โ€” automated capability review, not behavioral proof.

The curl|sh installation path is presented as an 'alternative' with an explicit review step (pipe through 'less' first), the preferred path is Homebrew, and the script is open-source MIT; the skill's core functionality is artifact policy scanning with well-documented external service use, which is not malicious.

โš  Flagged for review โ€” coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis โ€” not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

0
security
60
transparency
70
maintenance

Permission integrity

Makes network requests but does not declare curl/wget in required binaries

network_out

Installs packages at runtime โ€” transitive dependencies are not auditable

package_install

Findings (3)

Pattern match critical

Pipe-to-shell pattern (curl | sh) โ€” supply chain attack vector

SKILL.md ยท code ยท curl -sSfL https://raw.githubusercontent.com/Helixar-AI/ReleaseGuard/main/script

Pattern match critical

Pipe to sh โ€” executes piped content as shell commands

SKILL.md ยท code ยท | sh

Pattern match high

References sudo โ€” requests elevated privileges

SKILL.md ยท code ยท sudo

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class A/B). Final tier capped at Caution โ€” cannot be lifted by any downgrade, example-payload opt-in, or allowlist.

Permissions & capabilities

Requires 1 system binary.

package_installnetwork_out

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API