Versioned security assessment

Report ID: SA-17BE9E5A

6/30/2026, 4:18:27 AM

twitter-automation security assessment v2

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
twitter-automation
Version
v2
Maintainer
inference-sh-9
Source
github.com/inference-sh-9/skills/tree/main/skills/twitter-automation/
Coverage
1 Files scanned · 155 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

High

5 confirmed security findings require attention.

Installation context

Historical evidence

This report may not describe the currently installable artifact. Open the current Skill page for install guidance.

Open current Skill page

This report does not block or authorize the manifest or ZIP.

Static findings for Ruby or shell backtick execution are mostly false positives caused by Markdown code fences and inline command formatting. However, the skill includes a confirmed remote install script piped into sh and enables high-impact Twitter/X account actions through an external CLI, so publication should require human review and stronger safety guidance.

Report position

Historical report

Open audit history before using this report to install.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

1 Files scanned · 155 Lines analyzed

5 items shown for review

Limitations

This report does not claim runtime or sandbox execution and does not prove the absence of side effects.

Evidence chain

Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.

  1. Source

    Binding unavailable

  2. Artifact

    Identity incomplete

  3. Audit

    Complete

  4. Install contract

    Open manifest to verify

    Open manifest

Capabilities observed

Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.

Contains scripts

May execute code included with the Skill.

Not recorded by this audit

Network access

May connect to external services.

Observed in 6 evidence locations

Filesystem access

May read or write local files.

Observed in 3 evidence locations

Env variables

May read values from the process environment.

Not recorded by this audit

External commands

May invoke commands or programs outside the Skill.

Observed in 6 evidence locations

Risk findings

Confirmed security concerns are separated from items that still need review.

Confirmed security concerns (5)

RISK-001 High
SKILL.md:17
Remote Install Script Piped To Shell
The quick start runs a remote installer with curl and pipes it directly to sh before login. This is a true positive because it executes network-delivered code without requiring manual inspection first.
Line 17 directly pipes content from https://cli.inference.sh into sh. The surrounding install note claims checksum verification, but the execution pattern remains a recognized supply-chain risk.
RISK-002 High
SKILL.md:29-37SKILL.md:43-104
High-Impact Social Account Automation
The skill can post tweets, create media posts, like posts, retweet, delete posts, send direct messages, and follow users. These actions are legitimate for the skill purpose but can affect a user's public account, reputation, and private communications.
The listed apps and examples clearly include account-mutating Twitter/X actions. This is intended functionality, but it creates high impact if prompts or inputs are misused.
RISK-003 Medium
SKILL.md:4SKILL.md:20SKILL.md:43-104
External CLI Execution Is Core Functionality
The allowed tool declaration permits Bash execution for infsh commands, and the examples call inference.sh apps with user-controlled input values. This is expected behavior, but it depends on the external CLI and remote service handling inputs safely.
The skill intentionally invokes infsh from Bash and passes structured user content to remote apps. The command scope is narrower than arbitrary shell access, so the risk is moderate outside the install command.
RISK-004 Medium
SKILL.md:9-11SKILL.md:17-23SKILL.md:152-154
Network-Dependent Workflow
The skill references inference.sh, cloud-hosted media, installer URLs, documentation URLs, and remote media URLs. Network access is required for its purpose, but it should be disclosed because content and account actions leave the local environment.
The network URLs are explicit and central to the workflow. No evidence found of hidden exfiltration, but user content is sent to external services by design.
RISK-005 Low
SKILL.md:50SKILL.md:110SKILL.md:123
Local File Writes In Examples
Some examples save sample input or redirect generated media metadata into local JSON files. These writes are limited to relative filenames shown in documentation and do not target sensitive paths.
The file writes are explicit in the examples and use relative filenames. They are minor because no sensitive read path, overwrite target, or persistence behavior is shown.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable

Analysis metadata

Audit model: codex

Analysis state: Complete

Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.

Static false positives ignored (2)
Low
SKILL.md:15-21SKILL.md:29-37SKILL.md:43-148
Backtick Execution Findings Are Markdown False Positives
The many reported Ruby or shell backtick findings map to Markdown code fences, inline app identifiers, and command examples. No evidence found that SKILL.md contains executable Ruby backtick syntax.
The file is Markdown, and the backticks delimit code samples or inline command names. There is no Ruby source file or runtime context in the scanned file.
Low
SKILL.md:3SKILL.md:23SKILL.md:27
Weak Cryptography Findings Are Not Confirmed
The scanner reported weak cryptographic algorithm findings, but the visible cryptographic reference is SHA-256 checksum verification. No evidence found of MD5, SHA-1, or custom weak cryptography in the scanned file.
Line 23 describes SHA-256 verification, which is not a weak hash for checksum integrity. The other reported lines do not show cryptographic implementation evidence.

Verify and export

JSON report CITATION.cff SARIF 2.1.0 Signed installation manifest

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable