lint-and-validate
Pass
Audited by Gen Agent Trust Hub on Feb 20, 2026
Risk Level: SAFECOMMAND_EXECUTION
Full Analysis
- [COMMAND_EXECUTION] (LOW): The
scripts/lint_runner.pyscript executes local development commands such asnpm run lint,npx eslint,ruff, andmypyviasubprocess.run. - Evidence: The script constructs command lists (e.g.,
["npm", "run", "lint"]) and executes them in the context of the project being analyzed. - Context: This behavior is fundamental to the skill's purpose as a linter. The use of argument lists instead of raw shell strings provides protection against direct command injection.
- [DATA_EXPOSURE] (SAFE): The scripts read project configuration files and source code to perform analysis and generate coverage reports.
- Evidence:
lint_runner.pyreadspackage.jsonandpyproject.toml;type_coverage.pyreads.ts,.tsx, and.pyfiles. - Context: File access is restricted to the target project directory. No access to sensitive system directories (e.g., SSH keys, environment secrets) or exfiltration via network calls was found.
- [INDIRECT_PROMPT_INJECTION] (LOW): The skill ingests untrusted source code and metadata from the local filesystem for analysis.
- Ingestion points:
scripts/type_coverage.pyreads file content usingread_text(). - Boundary markers: No specific delimiters are used to wrap the ingested code content.
- Capability inventory: The skill can execute local commands through the
Bashtool and its own Python scripts. - Sanitization: No sanitization is performed on the file content before regex processing, though the output is limited to statistical data and coverage metrics.
- Context: While an attacker could place malicious instructions in code comments, the risk is inherent to static analysis tools and is mitigated here by the specialized nature of the output (regex-based metrics).
Audit Metadata