stata-run — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited stata-run (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
The argument is the Stata code or absolute path to a .do file to execute.
.do or .ado, call: stata_run(code=<argument>, is_file=True, echo=True, as_json=True)Otherwise call:
stata_run(code=<argument>, echo=True, as_json=True)success is true, display the stdout output. Note the output is truncated to 5,000 chars; if the response includes a log_path, offer to tail the full log with /stata-log <log_path>.success is false, display the error message and rc code. Suggest using /stata-lint <path> for syntax issues or /stata-help <command> for documentation./stata-graph can export them.If using background mode (background=True): you may do other work or fire parallel tasks, but you MUST call stata_task_status(task_id=<id>, wait=True, timeout=<N>, tail_lines=<M>) for every task before returning to the user. Set timeout to match expected runtime; set tail_lines to how much output you want inline vs. reading separately via stata_read_log. Loop on timeout until status is 'done' or 'failed'.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.