Installation¶
TestSeal requires Python 3.11 or newer. Git is required for working-tree, staged, and revision scans. A saved unified diff can be scanned without a Git repository.
Install as a project tool¶
Use this option when TestSeal belongs in the repository's development environment:
Pin the version in applications and shared CI images so policy changes are reviewed with dependency updates.
Install as an isolated command¶
Use an isolated installation when TestSeal should not share dependencies with the target project. The Python package has no runtime dependencies.
Run without a persistent installation:
Verify the installation¶
The commands should print the installed version, list the scan options, and
report one TS003 finding from the built-in example. If the
shell cannot find testseal, run it through the interpreter used for
installation:
Upgrade¶
Read the release notes before upgrading a blocking installation. Rule IDs retain their documented meaning, but matching precision, messages, and evidence can improve between releases.
Uninstall¶
TestSeal does not create a global account or send telemetry. Local report files and repository configuration remain under the repository owner's control.
Next step¶
Continue with your first scan.