PyPI / ty / 0.0.88

ty 0.0.88

Source

https://github.com/astral-sh/ty

Tag scanned

0.0.88

Compared with

0.0.87 (1 signals introduced since)

Files

40 scanned, 30 skipped (binary, oversized, or unrecognised)

Signals

0 critical · 0 warn · 7 info

Scan time

7.9 s

LLM review

Reviewed by claude-haiku-5-5 (Anthropic): 7 of 7 warn and critical signals; 7 demoted to info.

Disclude version

4.0.0

Scanned (UTC)

2026-10-15 16:40

Signals

Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.

1. info warn → info by review dynamic-execution docs/installation.md:74:5 new in this release

   [markup prose] pipeline feeds into `sh` — piped data is executed as shell code (ast pass, confidence 0.80)

       $ curl -LsSf https://astral.sh/ty/0.0.88/install.sh | sh

   likely benign LLM, confidence 0.90 Version-pinned documented curl | sh install command for ty.

   Reasoning

   Version-pinned curl | sh installer on the official domain, shown in install docs. Legitimate, though the pipe-to-shell pattern is inherently a trust decision for the reader.

2. info warn → info by review unicode-mixed-script README.md:102:36

   identifier `tiː` mixes scripts: Latin + Other (raw pass, confidence 0.80)

   
   It's pronounced as "tee - why" ([`/tiː waɪ/`](https://en.wikipedia.org/wiki/Help:IPA/English#Key))
   
   #### How should I stylize ty?

   dismissed LLM, confidence 0.97 IPA pronunciation symbols in the README's pronunciation note.

   Reasoning

   The flagged characters are IPA phonetic symbols in a pronunciation guide, a standard and legitimate use of Unicode in documentation. The mixed-script signal is a raw-pass false positive on prose.

3. info warn → info by review unicode-mixed-script README.md:102:41

   identifier `waɪ` mixes scripts: Latin + Other (raw pass, confidence 0.80)

   
   It's pronounced as "tee - why" ([`/tiː waɪ/`](https://en.wikipedia.org/wiki/Help:IPA/English#Key))
   
   #### How should I stylize ty?

   dismissed LLM, confidence 0.97 IPA pronunciation symbols in the README's pronunciation note.

   Reasoning

   Same IPA pronunciation text as the adjacent finding, inside a Markdown link label describing how to say the project name. Benign prose.

4. info warn → info by review dynamic-execution docs/installation.md:62:5

   [markup prose] pipeline feeds into `sh` — piped data is executed as shell code (ast pass, confidence 0.80)

       $ curl -LsSf https://astral.sh/ty/install.sh | sh

   likely benign LLM, confidence 0.90 Documented curl | sh install command for the ty tool.

   Reasoning

   This is the standard documented curl-to-sh installer for the project's official astral.sh domain, shown as a user instruction in markdown. The AST pass flags the pipe into sh, but this is documentation, not code the scanner executes. It is a common pattern, though it carries general supply-chain risk for users.

5. info warn → info by review dynamic-execution docs/installation.md:68:5

   [markup prose] pipeline feeds into `sh` — piped data is executed as shell code (ast pass, confidence 0.80)

       $ wget -qO- https://astral.sh/ty/install.sh | sh

   likely benign LLM, confidence 0.90 Documented wget | sh install command for the ty tool.

   Reasoning

   Documented wget | sh installer from the same official domain, shown as a user instruction in a markdown install guide. Legitimate documentation.

6. info warn → info by review encoding-base64 docs/reference/editor-settings.md:649:40

   base64-like blob (68 bytes, compression ratio 1.16) (raw pass, confidence 0.60)

   This setting is useful for debugging issues with the language server. Refer to the [troubleshooting
   guide](https://github.com/astral-sh/ty-vscode/blob/6cf16b4e87342a49f2bec1310a730cde8229e1d9/TROUBLESHOOTING.md)
   in [ty's VS Code extension][ty-vscode] for more information.

   dismissed LLM, confidence 0.95 Text in a documentation link that the base64 heuristic misread as an encoded blob.

   Reasoning

   The matched 'blob' is ordinary prose wrapped across lines in a Markdown link that includes a GitHub commit hash. The base64 heuristic fired on the text's letter patterns, which is a false positive on a raw-pass finding.

7. info critical → info by review dynamic-execution scripts/release.sh:75:1

   command name is a variable (`$script_root`) and `script_root` is assigned the output of a command — executed command determined at runtime (ast pass, confidence 0.90)

   
   "${script_root}/autogenerate_files.sh"
   git add ./docs/reference ./rust-toolchain.toml

   likely benign LLM, confidence 0.80 Release script invoking a sibling autogenerate_files.sh via a computed script directory path.

   Reasoning

   The variable command name is script_root, a directory path derived from command output, and the executed target is a sibling helper script (autogenerate_files.sh) in the same repo. This is a typical release-script pattern for invoking a local helper. The critical severity overstates the risk, but the runtime path resolution cannot be fully verified from the snippet.

Reproduce This Scan

Run disclude locally to verify. Add --format sarif for SARIF output. Add --llm (with an API key in the environment) to include the LLM review.

cargo install disclude --version 4.0.0
git clone https://github.com/astral-sh/ty ty && cd ty
git checkout 0.0.88
disclude scan --severity info --diff 0.0.87 .